CVE-2023-33859
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 Security QRadar EDR 3.12 could disclose sensitive information due to an observable login response discrepancy. IBM X-Force ID: 257697.
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 Security QRadar EDR 3.12 contains an information disclosure vulnerability in its login mechanism where the application returns distinguishable responses that could reveal sensitive information such as valid usernames or the existence of accounts, potentially aiding attackers in credential-based attacks.
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= 3.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm QRadar EDR versionAccess the IBM Security QRadar EDR administrative console or check the installed package version using system inventory tools (e.g., rpm -q ibm-qradar-edr, dpkg -l, or the application's About/Version page in the UI)Affected if version is 3.12 exactly (the only affected version listed)
-
Test login response with invalid usernameAttempt to log in with a clearly non-existent username (e.g., nonexistentuser123) and record the exact error message, response code, and any text differencesAffected if error message reveals whether the username exists or provides different feedback than a valid username would receive
-
Test login response with valid usernameAttempt to log in with a known-valid username but incorrect password, and compare the exact error message and response to the invalid username testAffected if the response differs from the invalid username case (e.g., mentions 'invalid password' vs 'user not found' or returns different HTTP status codes)
-
Compare error message specificityReview both login error responses side by side - check for wording that specifically indicates username validity (such as 'user does not exist' vs 'invalid credentials')Affected if error messages are distinguishable and reveal account existence rather than showing a generic 'invalid credentials' for both cases
A user is affected if QRadar EDR version 3.12 is installed AND the login mechanism returns distinguishable responses for valid vs invalid usernames, enabling user enumeration.
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 dataApply the vendor-supplied patch for CVE-2023-33859. As an interim control, implement generic error messages for login failures and rate-limiting on authentication endpoints to reduce enumeration opportunities.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33859 — 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-33859 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