Unauthenticated credential disclosure via reflected Web UI scripting
Published Nov 1, 2024 · Updated Nov 1, 2024
Reflected XSS in IBM CICS TX Standard 11.1 allows remote attackers to disclose credentials by injecting JavaScript into the Web UI. IBM identifies shipped Web UI pages as the locus but does not disclose the affected page, parameter, or missing output-neutralization operation. Exploitation is unauthenticated but requires a trusted-session user to follow or render attacker-controlled input; the resulting script can alter console behavior and expose credentials.
Summary
What happened
Reflected XSS in IBM CICS TX Standard 11.1 allows remote attackers to disclose credentials by injecting JavaScript into the Web UI. IBM identifies shipped Web UI pages as the locus but does not disclose the affected page, parameter, or missing output-neutralization operation. Exploitation is unauthenticated but requires a trusted-session user to follow or render attacker-controlled input; the resulting script can alter console behavior and expose credentials.
The record
- CVE
- CVE-2024-41745
- Published
- Nov 1, 2024
- Updated
- Nov 1, 2024
- Vendor
- IBM
- Product
- CICS TX Standard
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 1, 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=11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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