LiveActive security incident?Get immediate response
CVE Record

CVE-2023-33860: IBM Security ReaQta information disclosure

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Security QRadar EDR 3.12 may expose login or authorization cookies because they are not marked Secure. If those cookies are sent over an unencrypted HTTP connection, an attacker who can observe that traffic could capture them and potentially access protected information.

Executive priority

Prioritize this as a moderate confidentiality issue for affected EDR management environments. It is not currently supported as actively exploited, but exposed security tooling consoles should be remediated promptly because session cookie leakage can undermine administrative trust boundaries.

Technical view

CVE-2023-33860 is a CWE-614 cookie protection weakness in IBM Security QRadar EDR 3.12. Authorization tokens or session cookies lack the Secure attribute, creating an information disclosure risk when cookies traverse plaintext HTTP. The CVSS 3.1 score is 5.3, with low confidentiality impact only.

Likely exposure

Exposure appears limited to IBM Security QRadar EDR version 3.12. The source bundle marks other versions as unaffected by default. Organizations without this product and version are not indicated as affected by the provided sources.

Exploitation context

The provided sources do not show known active exploitation, and the CVE is not listed as KEV. Exploitation depends on cookies being sent over insecure HTTP and traffic being observable. Treat internet-accessible or broadly reachable EDR consoles as higher concern.

Researcher notes

Evidence is narrow and vendor-specific. The bundle identifies IBM Security QRadar EDR 3.12, CWE-614, CVSS 5.3, and cookie Secure-attribute omission. No exploit proof, patch version, workaround detail, or broader product impact is provided in the supplied sources.

Mitigation direction

  • Review IBM advisory 7159770 for fixed versions or official workarounds.
  • Identify any IBM Security QRadar EDR 3.12 deployments.
  • Apply IBM-provided updates or mitigations when confirmed by the advisory.
  • Restrict EDR console access to trusted networks while remediation is pending.
  • Avoid relying on configuration-only fixes unless IBM guidance supports them.

Validation and detection

  • Confirm whether IBM Security QRadar EDR 3.12 exists in asset inventory.
  • Review authenticated response cookies for the Secure attribute.
  • Verify cookies are not transmitted over plaintext HTTP after remediation.
  • Check access logs for unexpected HTTP access to the EDR interface.
  • Document affected instances, remediation status, and residual exceptions.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-614: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-33860 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-33860Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSecurity QRadar EDR3.12unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-614 · source CWE mapping

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.