CVE-2023-22875
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 · uneditedIBM QRadar SIEM 7.4 and 7.5copies certificate key files used for SSL/TLS in the QRadar web user interface to managed hosts in the deployment that do not require that key. IBM X-Force ID: 244356.
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 confidenceIBM QRadar SIEM 7.4 and 7.5 contains a vulnerability where SSL/TLS private certificate keys used for the web UI are unnecessarily copied to managed hosts in the deployment that do not require access to these keys, increasing the attack surface and exposing sensitive cryptographic material to additional systems.
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= 7.4.0= 7.5.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify QRadar versionRun 'qradar_version' command or check /opt/qradar/conf/qradar.conf for the version string. Compare against the affected versions 7.4.0 and 7.5.0.Affected if Version is exactly 7.4.0 or 7.5.0
-
Identify SSL/TLS private keys for web UILocate the private key files used for QRadar web UI HTTPS termination. Common locations include /etc/httpd/conf/ssl.key/ or /var/www/qradar_web_ui/ssl/. List files with .key or private key extensions.Affected if Private key files exist in the expected SSL certificate directories
-
List all hosts in the QRadar deploymentRun 'qconf -ha' or access the Admin console to view the list of all managed hosts, consoles, and collectors in the deployment.Affected if Multiple hosts exist beyond a single console (indicates a distributed deployment)
-
Check for private key presence on managed hostsOn each managed host (not the console), search for the same private key files found in step 2. Compare file fingerprints or names. Check directories like /etc/httpd/conf/ssl.key/ or similar SSL directories on managed hosts.Affected if Private keys for the web UI are found on hosts other than the primary console or dedicated UI servers
-
Confirm unnecessary key distributionIdentify which hosts actually require private keys for SSL/TLS termination (typically only the console or designated UI servers). Cross-reference with findings from step 4.Affected if Managed hosts that do not perform web UI SSL termination have copies of the private keys
If the QRadar version is 7.4.0 or 7.5.0 and the web UI private keys are present on managed hosts that do not require them for SSL/TLS termination, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReview certificate key distribution across the QRadar deployment and ensure private keys are only present on hosts that require them for SSL/TLS termination; consider key rotation if unauthorized access is suspected.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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