Service interruption via unchecked XID length allocation
Published Feb 4, 2022 · Updated Aug 3, 2024
Uncontrolled memory allocation in Apache Artemis before 2.19.1 allows remote attackers to interrupt broker availability via crafted XID packets. XidCodecSupport.decodeXid trusts attacker-supplied branch-qualifier and global-transaction identifier lengths and allocates byte arrays before validating them against readable buffer bytes. Network access to the broker's Core protocol is sufficient; a forged XA request can exhaust JVM memory and partially disrupt service.
Summary
What happened
Uncontrolled memory allocation in Apache Artemis before 2.19.1 allows remote attackers to interrupt broker availability via crafted XID packets. XidCodecSupport.decodeXid trusts attacker-supplied branch-qualifier and global-transaction identifier lengths and allocates byte arrays before validating them against readable buffer bytes. Network access to the broker's Core protocol is sufficient; a forged XA request can exhaust JVM memory and partially disrupt service.
The record
- CVE
- CVE-2022-23913
- Published
- Feb 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Artemis
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.19.0 <2.20.0 changes=[{"at":"2.19.1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo