OESA-2021-1462 (CVE-2021-44228)
Vulnerability from osv_openeuler – Published: 2021-12-11 11:04 – Updated: 2026-08-06 11:04 – Source websiteJava logging package.
Security Fix(es):
The details of a high-risk vulnerability in Apache Log4j2 have been disclosed. Attackers can use the vulnerability to execute code remotely. Some reports carry suspected POC; Apache Log4j2 is a Java-based logging tool. This tool rewrites the Log4j framework and introduces a large number of rich features. The log framework is widely used in business system development to record log information. In most cases, developers may write error messages caused by user input into the log. The trigger condition of this vulnerability is that as long as the data input by external users will be recorded in the log, it can cause remote code execution.(CVE-2021-44228)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"noarch": [
"log4j-2.13.2-2.oe1.noarch.rpm",
"log4j-bom-2.13.2-2.oe1.noarch.rpm",
"log4j-help-2.13.2-2.oe1.noarch.rpm",
"log4j-jcl-2.13.2-2.oe1.noarch.rpm",
"log4j-jmx-gui-2.13.2-2.oe1.noarch.rpm",
"log4j-nosql-2.13.2-2.oe1.noarch.rpm",
"log4j-slf4j-2.13.2-2.oe1.noarch.rpm",
"log4j-taglib-2.13.2-2.oe1.noarch.rpm",
"log4j-web-2.13.2-2.oe1.noarch.rpm"
],
"src": [
"log4j-2.13.2-2.oe1.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "log4j",
"purl": "pkg:rpm/openEuler/log4j\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.2-2.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"noarch": [
"log4j-2.13.2-2.oe1.noarch.rpm",
"log4j-bom-2.13.2-2.oe1.noarch.rpm",
"log4j-help-2.13.2-2.oe1.noarch.rpm",
"log4j-jcl-2.13.2-2.oe1.noarch.rpm",
"log4j-jmx-gui-2.13.2-2.oe1.noarch.rpm",
"log4j-nosql-2.13.2-2.oe1.noarch.rpm",
"log4j-slf4j-2.13.2-2.oe1.noarch.rpm",
"log4j-taglib-2.13.2-2.oe1.noarch.rpm",
"log4j-web-2.13.2-2.oe1.noarch.rpm"
],
"src": [
"log4j-2.13.2-2.oe1.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP2",
"name": "log4j",
"purl": "pkg:rpm/openEuler/log4j\u0026distro=openEuler-20.03-LTS-SP2"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.2-2.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Critical"
},
"details": "Java logging package.\n\nSecurity Fix(es):\n\nThe details of a high-risk vulnerability in Apache Log4j2 have been disclosed. Attackers can use the vulnerability to execute code remotely. Some reports carry suspected POC; Apache Log4j2 is a Java-based logging tool. This tool rewrites the Log4j framework and introduces a large number of rich features. The log framework is widely used in business system development to record log information. In most cases, developers may write error messages caused by user input into the log. The trigger condition of this vulnerability is that as long as the data input by external users will be recorded in the log, it can cause remote code execution.(CVE-2021-44228)",
"id": "OESA-2021-1462",
"modified": "2026-08-06T11:04:44Z",
"published": "2021-12-11T11:04:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1462"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-44228"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "log4j security update",
"upstream": [
"CVE-2021-44228"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.