Skip to content
Noroxi
CVE-2021-44832· NVD / CVE Program· CNA apache

Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

Noroxi assessment

Priority: Plan (action score 55/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 97.9% (FIRST EPSS); higher than 99.9% of all records.
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Apache Software Foundation Apache Log4j2 2.12.4, 2.3.2.
  • Mentioned 6 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to Apache Software Foundation Apache Log4j2 2.12.4, 2.3.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.6 · v3.1—Proof of concept Fix available
Published
Dec 28, 2021
Updated
Jun 17, 2026
EPSS
97.9% · 99th percentile

Report tools

JSON

Action score

55

Plan

Add it to your regular patch cycle.

CVSS
26 / 40 · 6.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
29 / 30 · 97.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-44832

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for apache records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachelog4j
oraclecommunications diameter signaling router
oraclecommunications interactive session recorder
oracleprimavera gateway
oracleprimavera p6 enterprise project portfolio management
oracleprimavera unifier
oracleretail assortment planning
oracleretail fiscal management
oraclesiebel ui framework
oracleweblogic server
ciscocloudcenter
fedoraprojectfedora

and 10 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache log4j2.0.1 and later · before 2.3.2
  • apache log4j2.4 and later · before 2.12.4
  • apache log4j2.13.0 and later · before 2.17.1
  • apache log4j2.0
  • cisco cloudcenter4.10.0.16
  • debian debian linux9.0
  • fedoraproject fedora34
  • fedoraproject fedora35
  • oracle communications brm - elastic charging enginebefore 12.0.0.4.6
  • oracle communications brm - elastic charging engine12.0.0.5.0
  • oracle communications diameter signaling router8.3.0.0 and later · up to 8.5.1.0 inclusive
  • oracle communications diameter signaling router8.0.0.0 and later · up to 8.5.1.0 inclusive
  • oracle communications interactive session recorder6.3
  • oracle communications interactive session recorder6.4
  • oracle communications offline mediation controllerbefore 12.0.0.4.4
  • oracle communications offline mediation controller12.0.0.5.0
  • oracle flexcube private banking12.1.0
  • oracle health sciences data management workbench2.5.2.1
  • oracle health sciences data management workbench3.0.0.0
  • oracle health sciences data management workbench3.1.0.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Log4j2

    • log4j-core and later · before 2.17.1affectedfixed in 2.12.4, 2.3.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12apache-log4j2before 2.17.1-12.17.1-1
Debian:9apache-log4j2before 2.12.4-0+deb9u12.12.4-0+deb9u1
Mavenorg.apache.logging.log4j:log4j-corefrom 2.0-beta7 · before 2.3.22.3.2
Mavenorg.apache.logging.log4j:log4j-corefrom 2.13.0 · before 2.17.12.17.1
Mavenorg.apache.logging.log4j:log4j-corefrom 2.4 · before 2.12.42.12.4
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.10.0 · before 1.10.91.10.9
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.11.0 · before 1.11.131.11.13
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.8.0 · before 1.9.21.9.2
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 2.0.0 · before 2.0.142.0.14
openSUSE:Leap 15.2log4jbefore 2.17.0-lp152.3.15.12.17.0-lp152.3.15.1
openSUSE:Leap 15.3log4jbefore 2.17.0-4.16.12.17.0-4.16.1
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-log4jbefore 0:2.17.1-1.redhat_00001.1.el7eap0:2.17.1-1.redhat_00001.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el8eap7-log4jbefore 0:2.17.1-1.redhat_00001.1.el8eap0:2.17.1-1.redhat_00001.1.el8eap

Same product

apache: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-44228Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpointsKEV
    100Now
  • CVE-2021-45046Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attackKEV
    96Now
  • CVE-2017-5645In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another applic
    66This week

Published before and after this one in the same product

  • ← EarlierCVE-2021-4104Dec 14, 2021 · Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2
    54Plan
  • ← EarlierCVE-2021-45105Dec 18, 2021 · Apache Log4j2 does not always protect from infinite recursion in lookup evaluation
    53Plan
  • Later →CVE-2022-23302Jan 18, 2022 · Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
    54Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Log4j22.12.4Vendor (CNA)
Apache Software Foundation Apache Log4j22.3.2Vendor (CNA)
debian:apache-log4j22.17.1-1 · Debian:12Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.12.4Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.17.1Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.3.2Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.10.9Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.11.13Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.9.2Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j22.0.14Package registry (OSV)
opensuse:log4j2.17.0-4.16.1 · openSUSE:Leap 15.3Package registry (OSV)
red hat:eap7-log4j0:2.17.1-1.redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:42021-12-29
Proof-of-concept repository on GitHubstars:12021-12-29

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayOct 24, 2026+1760 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (11 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records