Session cookie disclosure via missing Secure attribute
Published Mar 15, 2024 · Updated Aug 2, 2024
Sensitive-cookie exposure in IBM Sterling Secure Proxy 6.0.3 and 6.1.0 allows remote attackers to obtain session cookies over HTTP. The web session and authorization-token response logic emits sensitive cookies without the Secure attribute, allowing browsers to attach them to plaintext HTTP requests. Exploitation requires user interaction with an attacker-controlled HTTP link and network access sufficient to observe the resulting cleartext traffic.
Summary
What happened
Sensitive-cookie exposure in IBM Sterling Secure Proxy 6.0.3 and 6.1.0 allows remote attackers to obtain session cookies over HTTP. The web session and authorization-token response logic emits sensitive cookies without the Secure attribute, allowing browsers to attach them to plaintext HTTP requests. Exploitation requires user interaction with an attacker-controlled HTTP link and network access sufficient to observe the resulting cleartext traffic.
The record
- CVE
- CVE-2023-46179
- Published
- Mar 15, 2024
- Updated
- Aug 2, 2024
- Vendor
- IBM
- Product
- IBM Sterling Secure Proxy
- Classifications
- CWE-614, CAPEC-102, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 15, 2024CVE 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=6.0.3, 6.1.0
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