CVE-2019-4594
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 7.3.0 to 7.3.3 Patch 2 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-ForceID: 167810.
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 · high confidenceIBM QRadar 7.3.0 through 7.3.3 Patch 2 fails to properly enable HTTP Strict Transport Security (HSTS), which should instruct browsers to only communicate over HTTPS. Without HSTS enabled, a remote attacker positioned on the same network path (man-in-the-middle) can intercept session traffic and obtain sensitive information.
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.3.0, < 7.3.3= 7.3.3CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Determine the installed QRadar versionLog into the QRadar admin console and navigate to the 'About' page, or run 'qradar --version' from the console shell if availableAffected if The version displayed is 7.3.0, 7.3.1, 7.3.2, 7.3.3, or 7.3.3 Patch 1 or Patch 2 (the issue affects versions 7.3.0 through 7.3.3 Patch 2)
-
Verify HSTS header is absent in HTTP responsesUse a browser developer tool or curl command to inspect HTTP response headers when accessing the QRadar web interface over HTTP (not HTTPS). Run: curl -I http://<qradar_host>/ and look for the Strict-Transport-Security header in the responseAffected if The Strict-Transport-Security header is missing from HTTP responses (note: some implementations only send this header over HTTPS, which is also a configuration issue)
-
Check HSTS configuration in web server settingsExamine the QRadar web server configuration files (typically in /opt/qradar/conf or similar) for any HSTS-related directives. Check the Apache or nginx configuration if accessible. Look for 'Strict-Transport-Security' or 'HSTS' settingsAffected if No HSTS configuration exists, or the Strict-Transport-Security header is not configured to be sent to browsers
You are affected if your QRadar version is 7.3.0 through 7.3.3 Patch 2 AND HSTS is not enabled (the Strict-Transport-Security header is not being served to browsers).
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 data7.3.3
Enable HSTS on the QRadar web server/application by adding the Strict-Transport-Security header with an appropriate max-age value to ensure all communications occur over HTTPS and are protected from MITM interception.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4594 — 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-2019-4594 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