CVE-2019-4039
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 WebSphere MQ 8.0.0.0 through 8.0.0.9 and 9.0.0.0 through 9.1.1 could allow a local attacker to cause a denial of service within the error log reporting system. IBM X-Force ID: 156163.
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 WebSphere MQ versions 8.0.0.0-8.0.0.9 and 9.0.0.0-9.1.1 contain a local denial of service vulnerability in the error log reporting system. A local attacker with access to the system can cause the error logging to fail, potentially obscuring other issues or impacting monitoring capabilities.
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>= 8.0.0.0, <= 8.0.0.11>= 9.0.0.0, <= 9.0.0.5>= 9.1.0, <= 9.1.1>= 9.1.0.0, <= 9.1.0.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 installed WebSphere MQ versionRun the command 'dspmqver' on the system to display the version information for IBM WebSphere MQAffected if The version shown falls within 8.0.0.0-8.0.0.11, 9.0.0.0-9.0.0.5, or 9.1.0.0-9.1.1
-
Check for error log directory accessInspect the WebSphere MQ error log directory (default locations include /var/mqm/log or C:\Program Files\IBM\MQ\logs) and verify which user accounts have write access to these log directoriesAffected if Multiple local users or non-privileged accounts have write access to MQ error log directories, allowing them to trigger the logging failure
-
Verify MQ installation path and version fileCheck the version.ini or mqversion.txt file typically located in the MQ installation directory (such as /opt/mqm or C:\Program Files\IBM\MQ) to confirm the exact installed release and build levelAffected if The version file shows a release matching the affected ranges listed in CVE-2019-4039
The environment is affected if WebSphere MQ version 8.0.0.0-8.0.0.11, 9.0.0.0-9.0.0.5, or 9.1.0.0-9.1.1 is installed AND multiple local users have write access to the error logging directories.
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 IBM's patches for this vulnerability by updating WebSphere MQ to version 8.0.0.10 or later, or 9.1.2 or later. Since this is a local attack vector, also ensure proper access controls and least-privilege principles are followed for system access.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4039 — 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-4039 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