dbcve.org
Security Qradar EdrApplication · Ibm

CVE-2024-45642

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 3.12.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Security ReaQta 3.12 is vulnerable to cross-site scripting. This vulnerability allows a privileged user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Security ReaQta 3.12 contains a stored cross-site scripting (XSS) vulnerability in its web interface where a privileged user can inject arbitrary JavaScript code that gets stored and executes in the browsers of other users viewing the affected UI components, potentially allowing credential theft or session hijacking within trusted sessions.

MitigationImplement robust input validation and output encoding/sanitization for all user-supplied data rendered in the web UI; consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Security Qradar EdrApplication
Affected:>= 3.12, < 3.12.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Security Qradar EDR version
    Query the software inventory or use system information commands to retrieve the installed version of IBM Security Qradar EDR (formerly ReaQta). Check the application version through the product's built-in version check mechanism or system packages.
    Affected if The installed version is 3.12.0 through 3.11.x (any version >= 3.12 but < 3.12.12)
  2. Verify the web interface component is enabled
    Confirm that the web-based user interface component of IBM Security Qradar EDR is installed and running. Check if the UI service is active and accessible via HTTP/HTTPS.
    Affected if The web interface is accessible and users can interact with UI components where data is rendered
  3. Confirm privileged user access exists
    Review user account configurations to determine if any privileged user accounts (administrator, analyst, or similar elevated roles) exist in the system that have the capability to input or modify data displayed in the web UI.
    Affected if Privileged user accounts exist that can inject content into UI fields
  4. Check for stored user-supplied data in UI components
    Examine the application's database or configuration where user-generated content is stored and rendered. Identify any UI components that display user-supplied data without proper sanitization.
    Affected if User-supplied data fields are present and rendered in the web interface without evident output encoding

The environment is affected if IBM Security Qradar EDR version is 3.12 or higher but below 3.12.12 and the web interface with privileged user access is enabled, allowing stored XSS execution in user browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.12.12 or later
Fixed in 3.12.12
Interim mitigation

Implement robust input validation and output encoding/sanitization for all user-supplied data rendered in the web UI; consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

3.12.12

  1. Verify current installed version of IBM Security QRadar EDR
  2. Ensure you have a complete backup of the current configuration
  3. Schedule a maintenance window for the upgrade
  4. Download IBM Security QRadar EDR version 3.12.12 or later from IBM Fix Central or your authorized IBM distribution channel
  5. Follow IBM's standard upgrade procedure for QRadar EDR, typically involving running the installer or using the management console
  6. After upgrade, verify the new version is running and confirm the XSS vulnerability is resolved by testing that user input is properly sanitized

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Qradar Edr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45642 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data