Approved changes feed: RSS · Atom

cpe:2.3:a:apache:log4j:2.0:beta7:*:*:*:*:*:*

part: a version: 2.0 update: beta7

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductLog4J (c6e9988e-c7d3-5d36-aec2-f6066972a2bc)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/logging purl2cpe 2026-06-01 10:14:32.437156
pkg:deb/debian/apache-log4j2 purl2cpe 2026-06-01 10:14:32.437157
pkg:deb/ubuntu/apache-log4j2 purl2cpe 2026-06-01 10:14:32.437159
pkg:github/apache/log4j purl2cpe 2026-06-01 10:14:32.437160
pkg:maven/org.apache.logging.log4j/log4j purl2cpe 2026-06-01 10:14:32.437162
pkg:rpm/fedora/log4j purl2cpe 2026-06-01 10:14:32.437163
pkg:rpm/opensuse/log4j purl2cpe 2026-06-01 10:14:32.437164

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2021-44832 vulnerable 2026-06-08 05:36:47.516004 Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
Published: 2021-12-28T19:35:11.000Z
Updated: 2026-05-29T18:53:46.103Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.