Token disclosure via missing Secure cookie attribute
Published Jul 10, 2024 · Updated May 19, 2025
Sensitive-cookie exposure in IBM QRadar EDR 3.12 allows remote attackers to read authorization tokens or session cookies over HTTP. The web application creates authorization tokens or session cookies without the Secure attribute, so browsers can attach them to unencrypted HTTP requests. Exposure requires an affected browser to request an HTTP URL within the cookie's scope while an attacker can observe the network traffic.
Summary
What happened
Sensitive-cookie exposure in IBM QRadar EDR 3.12 allows remote attackers to read authorization tokens or session cookies over HTTP. The web application creates authorization tokens or session cookies without the Secure attribute, so browsers can attach them to unencrypted HTTP requests. Exposure requires an affected browser to request an HTTP URL within the cookie's scope while an attacker can observe the network traffic.
The record
- CVE
- CVE-2023-33860
- Published
- Jul 10, 2024
- Updated
- May 19, 2025
- Vendor
- IBM
- Product
- IBM QRadar EDR
- Classifications
- CWE-614, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2024CVE publishedPublication date reported by the CVE source.
- May 19, 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=3.12
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