Sensitive information decryption via risky cryptography
Published Feb 12, 2024 · Updated Aug 3, 2024
Use of risky cryptography in IBM CICS TX Standard and Advanced 11.1 allows remote attackers to decrypt sensitive information. IBM identifies weaker-than-expected cryptographic algorithms but does not disclose the affected protocol, algorithm, key handling, or code locus. Exploitation requires network reachability, no privileges or user interaction, and unspecified high-complexity conditions; the reported consequence is confidentiality loss without data alteration or service interruption.
Summary
What happened
Use of risky cryptography in IBM CICS TX Standard and Advanced 11.1 allows remote attackers to decrypt sensitive information. IBM identifies weaker-than-expected cryptographic algorithms but does not disclose the affected protocol, algorithm, key handling, or code locus. Exploitation requires network reachability, no privileges or user interaction, and unspecified high-complexity conditions; the reported consequence is confidentiality loss without data alteration or service interruption.
The record
- CVE
- CVE-2022-34309
- Published
- Feb 12, 2024
- Updated
- Aug 3, 2024
- Vendor
- IBM
- Product
- CICS TX Standard
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2024CVE 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=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