Session cookie disclosure via missing Secure attribute
Published Nov 13, 2023 · Updated Aug 30, 2024
Cookie protection failure in IBM CICS TX Advanced 10.1 allows remote attackers to obtain session cookies through cleartext HTTP. The authorization-token and session-cookie issuance path omits the Secure attribute, causing browsers to transmit those values over HTTP. A user must visit an attacker-supplied HTTP link, and the attacker must observe that traffic; exposure is limited to cookie confidentiality.
Summary
What happened
Cookie protection failure in IBM CICS TX Advanced 10.1 allows remote attackers to obtain session cookies through cleartext HTTP. The authorization-token and session-cookie issuance path omits the Secure attribute, causing browsers to transmit those values over HTTP. A user must visit an attacker-supplied HTTP link, and the attacker must observe that traffic; exposure is limited to cookie confidentiality.
The record
- CVE
- CVE-2023-38363
- Published
- Nov 13, 2023
- Updated
- Aug 30, 2024
- Vendor
- IBM
- Product
- CICS TX Advanced
- Classifications
- CWE-614, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 13, 2023CVE publishedPublication date reported by the CVE source.
- Aug 30, 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=10.1
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