JMS credential disclosure via sensitive trace data
Published Jan 18, 2025 · Updated Jan 21, 2025
Information disclosure in IBM App Connect Enterprise 12.0.1.0 through 12.0.7.0 and 13.0.1.0 lets remote authenticated users obtain JMS credentials. IBM maps the issue to improper management of sensitive trace data but does not identify the trace facility, storage location, or operation that exposes the credentials. Exploitation requires high privileges and a particular configuration; the documented consequence is disclosure of JMS credentials, with no integrity or availability impact.
Summary
What happened
Information disclosure in IBM App Connect Enterprise 12.0.1.0 through 12.0.7.0 and 13.0.1.0 lets remote authenticated users obtain JMS credentials. IBM maps the issue to improper management of sensitive trace data but does not identify the trace facility, storage location, or operation that exposes the credentials. Exploitation requires high privileges and a particular configuration; the documented consequence is disclosure of JMS credentials, with no integrity or availability impact.
The record
- CVE
- CVE-2024-49338
- Published
- Jan 18, 2025
- Updated
- Jan 21, 2025
- Vendor
- IBM
- Product
- App Connect Enterprise
- Classifications
- CWE-1323, T1552
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 18, 2025CVE publishedPublication date reported by the CVE source.
- Jan 21, 2025Record 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=12.0.1.0 <=12.0.7.0
- Affected versionversion=13.0.1.0
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