CVE-2023-46226
Published: 15 January 2024
Summary
CVE-2023-46226 is a critical-severity Code Injection (CWE-94) vulnerability in Apache Iotdb. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 12.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2023-46226 is a remote code execution vulnerability affecting Apache IoTDB versions 1.0.0 through 1.2.2. The flaw is tracked under CWE-94 and carries a CVSS 3.1 base score of 9.8, reflecting network-accessible attack vectors that require no authentication or user interaction.
An unauthenticated attacker with network access can exploit the issue to execute arbitrary code on the affected IoTDB instance, resulting in full compromise of confidentiality, integrity, and availability. The vulnerability stems from insufficient controls on code generation or execution paths reachable over the network.
Apache has published mitigation guidance directing users to upgrade to version 1.3.0, which resolves the flaw; the fix is detailed in the project’s security announcement and corresponding oss-security postings.
EPSS for the CVE rose from a low baseline to a recorded peak of 0.0645 before receding to the current value of 0.0344, indicating a period of increased exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0014
Vulnerability details
Remote Code Execution vulnerability in Apache IoTDB.This issue affects Apache IoTDB: from 1.0.0 through 1.2.2. Users are recommended to upgrade to version 1.3.0, which fixes the issue.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.
Dynamically generated code can be produced and executed inside the isolated chamber, preventing host compromise from code-injection payloads.
Validates inputs used in dynamic code generation to block injected directives.
Directly prevents execution of attacker-supplied code written into data memory regions.