CVE-2023-33860: CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in IBM Security QRadar EDR
IBM Security QRadar EDR 3.12 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.
AI Analysis
Technical Summary
CVE-2023-33860 is a medium-severity vulnerability affecting IBM Security QRadar EDR version 3.12. The issue arises because the product does not set the 'Secure' attribute on authorization tokens or session cookies. The 'Secure' attribute is a flag that instructs browsers to only send cookies over HTTPS connections, preventing their exposure over unencrypted HTTP traffic. Without this attribute, session cookies can be transmitted over insecure HTTP connections if a user follows a crafted HTTP link or visits a malicious site that triggers such a request. An attacker who can intercept this HTTP traffic (e.g., via a man-in-the-middle attack on an unsecured network) can capture these cookies and potentially hijack user sessions or gain unauthorized access. This vulnerability is classified under CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute), which highlights the risk of cookie exposure due to improper cookie attribute configuration. The CVSS 3.1 base score is 5.3 (medium), reflecting that the attack vector is network-based, requires no privileges or user interaction, and impacts confidentiality only, without affecting integrity or availability. No known exploits are currently reported in the wild, but the vulnerability presents a realistic risk in environments where users might be tricked into accessing HTTP links or where network traffic can be intercepted. Since QRadar EDR is a security monitoring and incident detection platform, compromising session cookies could allow attackers to access sensitive security data or manipulate detection capabilities, undermining organizational security posture.
Potential Impact
For European organizations using IBM Security QRadar EDR 3.12, this vulnerability could lead to unauthorized access to security monitoring consoles if attackers successfully capture session cookies. This exposure risks confidentiality of sensitive security event data, potentially allowing attackers to evade detection or manipulate incident response processes. The impact is particularly significant for organizations in critical infrastructure sectors, finance, government, and large enterprises that rely on QRadar EDR for threat detection and response. Given the medium severity and the requirement for interception of HTTP traffic, the risk is higher in environments where users access management consoles over insecure networks or where phishing/social engineering could direct users to HTTP links. The vulnerability does not directly affect system integrity or availability but compromises the confidentiality of session tokens, which can have cascading effects on security operations. European organizations with strict data protection regulations (e.g., GDPR) must consider the risk of unauthorized access to security logs and incident data as a compliance concern.
Mitigation Recommendations
1. Immediate mitigation involves ensuring that all access to IBM Security QRadar EDR consoles and related web interfaces is strictly over HTTPS, with HTTP access disabled or redirected to HTTPS to prevent cookie transmission over insecure channels. 2. IBM or administrators should apply patches or configuration updates that explicitly set the 'Secure' attribute on all session and authorization cookies to enforce secure transmission. 3. Network-level protections such as enforcing HTTPS via web application firewalls (WAFs), secure reverse proxies, or SSL/TLS termination points can help mitigate risks. 4. User education to avoid clicking on HTTP links related to QRadar EDR and to verify URLs before access can reduce phishing risks. 5. Implement network segmentation and VPN usage for accessing management consoles to reduce exposure to man-in-the-middle attacks. 6. Monitor logs for suspicious session activity that could indicate session hijacking attempts. 7. Regularly review and update security policies to enforce secure cookie handling and session management best practices.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Belgium, Sweden, Poland, Finland
CVE-2023-33860: CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in IBM Security QRadar EDR
Description
IBM Security QRadar EDR 3.12 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.
AI-Powered Analysis
Technical Analysis
CVE-2023-33860 is a medium-severity vulnerability affecting IBM Security QRadar EDR version 3.12. The issue arises because the product does not set the 'Secure' attribute on authorization tokens or session cookies. The 'Secure' attribute is a flag that instructs browsers to only send cookies over HTTPS connections, preventing their exposure over unencrypted HTTP traffic. Without this attribute, session cookies can be transmitted over insecure HTTP connections if a user follows a crafted HTTP link or visits a malicious site that triggers such a request. An attacker who can intercept this HTTP traffic (e.g., via a man-in-the-middle attack on an unsecured network) can capture these cookies and potentially hijack user sessions or gain unauthorized access. This vulnerability is classified under CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute), which highlights the risk of cookie exposure due to improper cookie attribute configuration. The CVSS 3.1 base score is 5.3 (medium), reflecting that the attack vector is network-based, requires no privileges or user interaction, and impacts confidentiality only, without affecting integrity or availability. No known exploits are currently reported in the wild, but the vulnerability presents a realistic risk in environments where users might be tricked into accessing HTTP links or where network traffic can be intercepted. Since QRadar EDR is a security monitoring and incident detection platform, compromising session cookies could allow attackers to access sensitive security data or manipulate detection capabilities, undermining organizational security posture.
Potential Impact
For European organizations using IBM Security QRadar EDR 3.12, this vulnerability could lead to unauthorized access to security monitoring consoles if attackers successfully capture session cookies. This exposure risks confidentiality of sensitive security event data, potentially allowing attackers to evade detection or manipulate incident response processes. The impact is particularly significant for organizations in critical infrastructure sectors, finance, government, and large enterprises that rely on QRadar EDR for threat detection and response. Given the medium severity and the requirement for interception of HTTP traffic, the risk is higher in environments where users access management consoles over insecure networks or where phishing/social engineering could direct users to HTTP links. The vulnerability does not directly affect system integrity or availability but compromises the confidentiality of session tokens, which can have cascading effects on security operations. European organizations with strict data protection regulations (e.g., GDPR) must consider the risk of unauthorized access to security logs and incident data as a compliance concern.
Mitigation Recommendations
1. Immediate mitigation involves ensuring that all access to IBM Security QRadar EDR consoles and related web interfaces is strictly over HTTPS, with HTTP access disabled or redirected to HTTPS to prevent cookie transmission over insecure channels. 2. IBM or administrators should apply patches or configuration updates that explicitly set the 'Secure' attribute on all session and authorization cookies to enforce secure transmission. 3. Network-level protections such as enforcing HTTPS via web application firewalls (WAFs), secure reverse proxies, or SSL/TLS termination points can help mitigate risks. 4. User education to avoid clicking on HTTP links related to QRadar EDR and to verify URLs before access can reduce phishing risks. 5. Implement network segmentation and VPN usage for accessing management consoles to reduce exposure to man-in-the-middle attacks. 6. Monitor logs for suspicious session activity that could indicate session hijacking attempts. 7. Regularly review and update security policies to enforce secure cookie handling and session management best practices.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- ibm
- Date Reserved
- 2023-05-23T00:32:05.086Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682cd0f81484d88663aeb5e2
Added to database: 5/20/2025, 6:59:04 PM
Last enriched: 7/4/2025, 2:10:34 PM
Last updated: 10/16/2025, 3:13:21 PM
Views: 31
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-61543: n/a
UnknownCVE-2025-61541: n/a
UnknownCVE-2025-61536: n/a
UnknownCVE-2025-41254: CWE-352: Cross-Site Request Forgery (CSRF) in VMware Spring Framework
MediumCVE-2025-36002: Password in Configuration File in IBM Sterling B2B Integrator
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.