CyberSecBulletin
CVE-2022-23302NVD status: Modified

Apache Log4j 1.x: Deserialization of Untrusted Data

Published Updated By the CyberSecBulletin desk

CVE-2022-23302 is a high-severity deserialization of untrusted data vulnerability in Apache Log4j 1.x from Apache, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.0-alpha1 as the first without the flaw, so updating Apache Log4j 1.x to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 63.8% chance of exploitation within 30 days, which is in the top 0.76% of all scored CVEs.

Patch now

Exploitation in the next 30 days is more likely than not, according to EPSS.

What to do

  1. Update Apache Log4j 1.x to 2.0-alpha1 or a later version.
  2. Update Reload4j to 1.2.18.1 or a later version.
  3. Update Communications Offline Mediation Controller to 12.0.0.4.4 or a later version.
  4. Read the advisory on lists.apache.org for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache Log4j 1.x1.0.1; before 2.0-alpha12.0-alpha1
ApacheLog4j1.0.1 through 1.2.17Not stated
NetAppSnapmanagerNot specified in the recordNot stated
BroadcomBrocade SannavNot specified in the recordNot stated
QosReload4jbefore 1.2.18.11.2.18.1
OracleAdvanced Supply Chain Planning12.1; 12.2Not stated
OracleBusiness Intelligence5.9.0.0.0; 12.2.1.3.0; 12.2.1.4.0Not stated
OracleBusiness Process Management Suite12.2.1.3.0; 12.2.1.4.0Not stated
OracleCommunications Eagle FTP Table Base Retrieval4.5Not stated
OracleCommunications Instant Messaging Server10.0.1.5.0Not stated
OracleCommunications Messaging Server8.1Not stated
OracleCommunications Network Integrity7.3.6Not stated
OracleCommunications Offline Mediation Controllerbefore 12.0.0.4.4; 12.0.0.5.012.0.0.4.4
OracleCommunications Unified Inventory Management7.4.1; 7.4.2Not stated
OracleE-business Suite Cloud Manager And Cloud Backup Modulebefore 2.2.1.1.1; 2.2.1.1.12.2.1.1.1
OracleEnterprise Manager Base Platform13.4.0.0; 13.5.0.0Not stated
OracleFinancial Services Revenue Management And Billing Analytics2.7.0.0; 2.7.0.1; 2.8.0.0Not stated
OracleHealthcare Foundation8.1.0Not stated
OracleHyperion Data Relationship Managementbefore 11.2.8.011.2.8.0
OracleHyperion Infrastructure Technologybefore 11.2.8.011.2.8.0
OracleIdentity Management Suite12.2.1.3.0; 12.2.1.4.0Not stated
OracleIdentity Manager Connector11.1.1.5.0Not stated
OracleJdeveloper12.2.1.3.0Not stated
OracleMiddleware Common Libraries And Tools12.2.1.4.0Not stated
OracleMySQL Enterprise Monitor8.0.29 and earlierNot stated

Version data comes from the organisation that assigned the CVE; 2 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighNVD
CVSS 3.18.8HighCISA (ADP)
CVSS 2.06.0MediumNVD

Official description

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How developers prevent this class of flaw

  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Explicitly define a final object() to prevent deserialization.

More Deserialization of Untrusted Data vulnerabilities (CWE-502)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Third-party and government advisories

Other vulnerabilities in Apache Log4j 1.x

All Apache Log4j 1.x vulnerabilities

Recent Deserialization of Untrusted Data vulnerabilities

Spotted an error? Tell us.