BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-23305High confidence

SQL injection in JDBC Appender in Apache Log4j V1

Apache Software Foundation · Apache Log4j 1.x

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 66.54% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache Log4j 1.x and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
mavenlog4j:log4j<= 1.2.17Not statedGitHub advisory ↗github reviewed aggregator · 8 Jun 2026
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17<= 2.0Not statedGitHub advisory ↗github reviewed aggregator · 8 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-23305 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylog4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender
9 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • log4j as a component of A-MQ Clients 2
  • log4j as a component of Red Hat AMQ Broker 7
  • log4j as a component of Red Hat JBoss Fuse Service Works 6
  • log4j as a component of Red Hat JBoss Operations Network 3
  • openshift4/ose-metering-hadoop as a component of Red Hat OpenShift Container Platform 4
  • openshift4/ose-metering-hive as a component of Red Hat OpenShift Container Platform 4
  • openshift4/ose-metering-presto as a component of Red Hat OpenShift Container Platform 4
  • opendaylight as a component of Red Hat OpenStack Platform 13 (Queens)
  • opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens)
Summary
A flaw was found in the Java logging library Apache Log4j in version 1.x. JDBCAppender in Log4j 1.x is vulnerable to SQL injection in untrusted data. This allows a remote attacker to run SQL statements in the database if the deployed application is configured to use JDBCAppender with certain interpolation tokens.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-0477

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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.

What

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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.

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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.

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-89 ↗

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-89
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-0132Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2022-1769Oracle E-Business Suite: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle E-Business Suite ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2024-2180Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2893Oracle Hyperion: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Hyperion ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2024-1926Red Hat JBoss Enterprise Application Platform: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat JBoss Enterprise Application Platform auf Red Hat Enterprise Linux ausnutzen, um beliebigen Programmcode auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen preiszugeben, Dateien und Daten zu manipulieren oder Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0064Juniper Produkte: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter, anonymer, authentisierter, lokaler oder physischer Angreifer kann mehrere Schwachstellen in Juniper JUNOS, Juniper JUNOS Evolved, Juniper SRX Series, Juniper EX Series, Juniper QFX Series, Juniper ACX Series, Juniper PTX Series und Juniper MX Series ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen und seine Berechtigungen zu erweitern.

Official advisory ↗
BSI · German · WID-SEC-2023-1809Oracle Enterprise Manager: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1027Oracle Utilities Applications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Utilities Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2022-0169Oracle MySQL: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle MySQL ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2022-0521Apache log4j: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um beliebigen Programmcode auszuführen oder einen SQL-Injection durchzuführen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV22-035Red Hat security advisory (AV22-035)

Between 17 and 18 January 2022 Red Hat published Security Advisories to address vulnerabilities in the following products: Exploitation of these vulnerabilities could lead to remote code execution or privilege escalation.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20220119Security Bulletin 19 Jan 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Jan 2022, published on 19 January 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0281Multiples vulnérabilités dans les produits Splunk

rd?id=CVE-2020-1712 Référence CVE CVE-2020-17521 https://www.cve.org/CVERecord?id=CVE-2020-17521 Référence CVE CVE-2020-36518 https://www.cve.org/CVERecord?id=CVE-2020-36518 Référence CVE CVE-2021-33910 https://www.cve.org/CVERecord?id=CVE-2021-33910 Référence CVE CVE-2021-35937 https://www.cve.org/CVERecord?id=CVE-2021-35937 Référence CVE CVE-2021-35938 https://www.cve.org/CVERecord?id=CVE-2021-35938 Référence CVE CVE-2021-35939 https://www.cve.org/CVERecord?id=CVE-2021-35939 Référence CVE CVE-2021-46877 https://www.cve.org/CVERecord?id=CVE-2021-46877 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-31159 https://www.cve.org/CVERecord?id=CVE-2022-31159 Référence CVE CVE-2022-3821 https://www.cve.org/CVERecord?id=CVE-2022-3821 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2023-26118 https://www.cve.org/CVERecord?id=CVE-2023-26118 Référence CVE CVE-2023-26464 https://www.cve.org/CVERecord?id=CVE-2023-26464 Référence CVE CVE-2023-26604 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0419Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2018-11770 Référence CVE CVE-2018-11804 https://www.cve.org/CVERecord?id=CVE-2018-11804 Référence CVE CVE-2018-17190 https://www.cve.org/CVERecord?id=CVE-2018-17190 Référence CVE CVE-2019-17571 https://www.cve.org/CVERecord?id=CVE-2019-17571 Référence CVE CVE-2020-13936 https://www.cve.org/CVERecord?id=CVE-2020-13936 Référence CVE CVE-2020-9488 https://www.cve.org/CVERecord?id=CVE-2020-9488 Référence CVE CVE-2020-9493 https://www.cve.org/CVERecord?id=CVE-2020-9493 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-46751 https://www.cve.org/CVERecord?id=CVE-2022-46751 Référence CVE CVE-2023-22946 https://www.cve.org/CVERecord?id=CVE-2023-22946 Référence CVE CVE-2023-25613 https://www.cve.org/CVERecord?id=CVE-2023-25613 Référence CVE CVE-2023-26145 https://www.cve.org/CVERecord?id=CVE-2023-26145 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-26464 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0027Multiples vulnérabilités dans les produits Juniper Networks

VERecord?id=CVE-2022-1462 Référence CVE CVE-2022-1679 https://www.cve.org/CVERecord?id=CVE-2022-1679 Référence CVE CVE-2022-1789 https://www.cve.org/CVERecord?id=CVE-2022-1789 Référence CVE CVE-2022-20141 https://www.cve.org/CVERecord?id=CVE-2022-20141 Référence CVE CVE-2022-21699 https://www.cve.org/CVERecord?id=CVE-2022-21699 Référence CVE CVE-2022-2196 https://www.cve.org/CVERecord?id=CVE-2022-2196 Référence CVE CVE-2022-22164 https://www.cve.org/CVERecord?id=CVE-2022-22164 Référence CVE CVE-2022-22942 https://www.cve.org/CVERecord?id=CVE-2022-22942 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-25265 https://www.cve.org/CVERecord?id=CVE-2022-25265 Référence CVE CVE-2022-2663 https://www.cve.org/CVERecord?id=CVE-2022-2663 Référence CVE CVE-2022-2795 https://www.cve.org/CVERecord?id=CVE-2022-2795 Référence CVE CVE-2022-2873 https://www.cve.org/CVERecord?id=CVE-2022-2873 Référence CVE CVE-2022-2964 https://www.cve.org/CVERecord?id=CVE-2022-2964 Référence CVE CVE-2022-3028 https://www.cve.org/CVERecord?id=CVE-2022-3028 Référence CVE CVE-2022-30594 https://www.cve.org/CVERecord?id=CVE-2022-3

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0910Multiples vulnérabilités dans IBM QRadar

De multiples vulnérabilités ont été découvertes dans IBM QRadar. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-755Multiples vulnérabilités dans IBM Spectrum

De multiples vulnérabilités ont été découvertes dans IBM Spectrum. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-657Multiples vulnérabilités dans Oracle E-Business Suite

De multiples vulnérabilités ont été découvertes dans Oracle E-Business Suite. Elles permettent à un attaquant de provoquer une exécution de code arbitraire, une atteinte à l'intégrité des données et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-369Multiples vulnérabilités dans Oracle WebLogic Server

De multiples vulnérabilités ont été découvertes dans Oracle WebLogic Server. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à l'intégrité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-003903Apache Log4j における SQL インジェクションの脆弱性

Apache Log4j には、SQL インジェクションの脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5474Apache Log4j 보안 업데이트 권고(CVE-2021-45105, 44832, CVE-2022-23302, 23305, 23307) (Update. 22-1-21 17:00)

21-12-20 : 조치방안 내 오타 수정 2021-12-22 : 대응방안 업데이트(Java 6, 7 대상) 2021-12-29 : CVE-2021-44832 취약점 보안 업데이트 2021-12-30 : Log4j 2.12.4, 2.3.2 다운로드 추가 2021-12-31 : 영향을 받는 부분 수정 2022-1-3 : 영향받는 버전 수정 2022-1-21 : CVE-2022-23302, 23305, 23307 취약점 관련 내용 추가 ##### □ 개요 o Apache 소프트웨어 재단은 자사의 Log4j에서 발생하는 취약점을 해결한 보안 업데이트 권고[1] o 공격자는 해당 취약점을 이용하여 정상 서비스 중지 등의 피해를 발생시킬수 있으므로, 최신 버전으로 업데이트 권고 ※ Log4j 취약점을 이용한 침해사고 발생시 한국인터넷진흥원에 신고해 주시기 바랍니다. ##### □ 주요 내용 o Apache Log4j 2에서 발생하는 서비스 거부 취약점(CVE-2021-45105)[2] o Apache Log4j 2에서 발생하는 원격코드 실행 취약점(CVE-2021-44832)[4] o Apache Log4j 1에서 발생하는 원격 코드 실행 취약점(CVE-2022-23302)[6] o Apache Log4j 1에서 발생하는 SQL Injection 취약점(CVE-2022-23305)[6] o Apache Log4j 1에서 발생하는 원격 코드 실행 취약점(CVE-2022-23307)[6] ※ Log4j : 프로그램 작성 중 로그를 남기기 위해 사용되는 자바 기반의 오픈소스 유틸리티 ##### □ 영향을 받는 버전 o CVE-2021-45105 - 2.0-alpha1 ~ 2.16.0 버전 ※ 취약점이 해결된 버전 제외(Log4j 2.3.1, 2.12.3 및 이후 업데이트 버전 제외) o CVE-2021-44832 - 2.0-beta7 ~ 2.17.0 버전 ※ 취약점이 해결된 버전 제외(Log4j 2.3.2, 2.12.4 및 이후 업데이트 버전 제외) o CVE-2022-23302 - 1.x 버전 ※ JMSSink를 사용하지 않는 경우 취약점 영향 없음 o CVE-2022-23305 - 1.x 버전 ※ JDBCAppender를 사용하지 않는 경우 취약점 영향 없음 o CVE-2022-23307 - 1.x 버전 ※ Chainsaw를 사용하지 않는 경우 취약점 영향 없음 ##### □ 대응방안 o 제조사 홈페이지를 통해 최신버전으로 업데이트 적용[3] ※ 제조사 홈페이지에 신규버전이 계속 업데이트되고 있어 확인 후 업데이트 적용 필요 - Java 8 이상 : Log4j 2.17.1 이상 버전으로 업데이트 - Java 7 : Log

Official advisory ↗
NCSC-NL · Dutch · NCSC-2024-0418Kwetsbaarheden verholpen in Oracle Analytics

Een kwaadwillende kan de kwetsbaarheden misbruiken om aanvallen uit te voeren die kunnen leiden tot de volgende categorieën schade: - Denial-of-Service - Manipuleren van data - Uitvoer van willekeurige code (Gebruikersrechten) - Uitvoer van willekeurige code (Administratorrechten) - Toegang tot gevoelige gegevens

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 18 Jan 2022 · Last source change 27 May 2026, 13:40 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-0477
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.2.1 < unspecified; unspecified < 2.0-alpha1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    1.2.1 < unspecified; unspecified < 2.0-alpha1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j as a component of A-MQ Clients 2; log4j as a component of Red Hat AMQ Broker 7; log4j as a component of Red Hat JBoss Fuse Service Works 6; log4j as a component of Red Hat JBoss Operations Network 3; openshift4/ose-metering-hadoop as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-hive as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-presto as a component of Red Hat OpenShift Container Platform 4; opendaylight as a component of Red Hat OpenStack Platform 13 (Queens); opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens) · Fixed: log4j-0:1.2.14-6.6.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.6.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.6.el6_10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.6.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.6.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.6.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.6.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-scanner-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; and 543 more
    After
    log4j as a component of A-MQ Clients 2; log4j as a component of Red Hat AMQ Broker 7; log4j as a component of Red Hat JBoss Fuse Service Works 6; log4j as a component of Red Hat JBoss Operations Network 3; openshift4/ose-metering-hadoop as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-hive as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-presto as a component of Red Hat OpenShift Container Platform 4; opendaylight as a component of Red Hat OpenStack Platform 13 (Queens); opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens) · Fixed: log4j-0:1.2.14-6.6.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.6.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.6.el6_10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.6.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.6.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.6.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.6.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-scanner-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; and 542 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2022-0477↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Vendor advisory↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-23305 · cve.blacktree.nl