Information disclosure via JBoss client memory leak
Published Mar 11, 2022 · Updated Aug 2, 2024
Memory leak in JBoss-client 1.7 allows remote attackers to cause information disclosure by repeatedly using UserTransaction. The EJB remote transaction client retains memory after repeated UserTransaction operations instead of releasing it at the end of its effective lifetime. Reaching the condition requires repeated transaction activity; exhaustion can interrupt service and expose residual process data.
Summary
What happened
Memory leak in JBoss-client 1.7 allows remote attackers to cause information disclosure by repeatedly using UserTransaction. The EJB remote transaction client retains memory after repeated UserTransaction operations instead of releasing it at the end of its effective lifetime. Reaching the condition requires repeated transaction activity; exhaustion can interrupt service and expose residual process data.
The record
- CVE
- CVE-2022-0853
- Published
- Mar 11, 2022
- Updated
- Aug 2, 2024
- Vendor
- Red Hat
- Product
- Red Hat JBoss Enterprise Application Platform
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=1.7
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
- CVE-2022-0853 exploit repositoryproof of concept · unverified
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