HighCVE-2021-4104

    Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2 (CVE-2021-4104)

    Published Sources: BSI, CVE.org, OSV, SingCERT

    What is affected, what to do

    JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228.

    The vulnerability is being actively exploited; treat it as a priority. Update communications_offline_mediation_controller to version 12.0.0.4.0, hyperion_data_relationship_management to version 11.2.8.0, hyperion_infrastructure_technology to version 11.2.8.0.

    Affected
    • Apache Log4j 1.x eq Apache Log4j 1.2 1.2.x..Apache Log4j 1.2 1.2.x

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI, CVE.org, OSV, SingCERT

    80.6 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.62

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    117.07 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: ANSSI / CERT-FR How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    80.6 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.62
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 20 December 2023
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-502

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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: BSI CSAF, BSI WID Portal, NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5, CSA/SingCERT

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Apache Software FoundationApache Log4j 1.x
    • Apache Log4j 1.2 1.2.x
    • —
    apachelog4j
    • 1.2
    • —
    oracleadvanced_supply_chain_planning
    • 12.2
    • 12.1
    • —
    • —
    oraclebusiness_intelligence
    • 12.2.1.4.0
    • 12.2.1.3.0
    • 5.9.0.0.0
    • —
    • —
    • —
    oraclebusiness_process_management_suite
    • 12.2.1.4.0
    • 12.2.1.3.0
    • —
    • —
    oraclecommunications_eagle_ftp_table_base_retrieval
    • 4.5
    • —
    oraclecommunications_messaging_server
    • 8.1
    • —
    oraclecommunications_network_integrity
    • 7.3.6
    • —
    oraclecommunications_offline_mediation_controller
    • < 12.0.0.4.0
    • 12.0.0.5.0
    • 12.0.0.4.0
    • —
    oraclecommunications_unified_inventory_management
    • 7.4.1
    • 7.3.5
    • 7.3.4
    • 7.4.2
    • —
    • —
    • —
    • —
    oraclee-business_suite_cloud_manager_and_cloud_backup_module
    • 2.2.1.1.1
    • —
    oracleenterprise_manager_base_platform
    • 13.4.0.0
    • 13.5.0.0
    • —
    • —
    oraclefinancial_services_revenue_management_and_billing_analytics
    • 2.7.0.0
    • 2.7.0.1
    • 2.8.0.0
    • —
    • —
    • —
    oraclefusion_middleware_common_libraries_and_tools
    • 12.2.1.4.0
    • —
    oraclegoldengate
    • —
    • —
    oraclehealthcare_data_repository
    • 8.1.0
    • —
    oraclehyperion_data_relationship_management
    • < 11.2.8.0
    • 11.2.8.0
    oraclehyperion_infrastructure_technology
    • < 11.2.8.0
    • 11.2.8.0
    oracleidentity_management_suite
    • 12.2.1.3.0
    • 12.2.1.4.0
    • —
    • —
    oraclejdeveloper
    • 12.2.1.3.0
    • —
    oraclemysql_enterprise_monitor
    • ≤ 8.0.29
    • —
    oracleretail_allocation
    • 14.1.3.2
    • 16.0.3
    • 15.0.3.1
    • 19.0.1
    • —
    • —
    • —
    • —
    oracleretail_extract_transform_and_load
    • 13.2.5
    • —
    oraclestream_analytics
    • —
    • —
    oracletimesten_grid
    • —
    • —
    oracletuxedo
    • 12.2.2.0.0
    • —
    oracleutilities_testing_accelerator
    • 6.0.0.1.1
    • 6.0.0.2.2
    • 6.0.0.3.1
    • —
    • —
    • —
    oracleweblogic_server
    • 12.2.1.3.0
    • 14.1.1.0.0
    • 12.2.1.4.0
    • —
    • —
    • —
    redhatcodeready_studio
    • 12.0
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxredhatenterprise_linux6.0
    Linuxredhatenterprise_linux7.0
    Linuxredhatenterprise_linux8.0
    Otherfedoraprojectfedora35

    Weakness classes (CWE)

    • CWE-502Deserialization of Untrusted Data

      Base

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

      Entry at MITRE CWE-502

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    ANSSI / CERT-FRLicence Ouverte 2.0, as of CERTFR-2021-ALE-022 – [MaJ] Vulnérabilité dans Apache Log4j (clôturée 2022-05-04) (opens in a new tab)cert.cyber.gouv.fractively exploited

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2021-4104
    <a href="https://intel.neosec.eu/en/cve/CVE-2021-4104"><img src="https://intel.neosec.eu/badge/cve/CVE-2021-4104.svg?lang=en" alt="CVE-2021-4104 – NEOSEC Intel" height="20"></a>