CVE-2018-1925
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 WebShere MQ 9.1.0.0, 9.1.0.1, 9.1.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 152925.
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 9.1.0.0, 9.1.0.1, and 9.1.1 use weaker than expected cryptographic algorithms, which could allow an attacker to decrypt highly sensitive information transmitted through or stored in the message queue system.
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>= 9.1.0.0, <= 9.1.0.1= 9.1.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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/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 installed IBM WebSphere MQ versionRun the command 'dspmqver' or check the installation directory for the version file. On Linux/Unix, you can also source the mqsiprofile and run 'mqversion'. On Windows, check the Programs and Features list or the installation path.Affected if The installed version is 9.1.0.0, 9.1.0.1, or 9.1.1
-
Identify if SSL/TLS channels are configuredRun the MQSC command 'DISPLAY CHANNEL(*) SSLCIPH' against the queue manager using runmqsc, or check the queue manager's qm.ini file for SSL or TLS channel definitions.Affected if Any SSL or TLS channels are defined and active, indicating the queue manager transmits encrypted data
-
Review SSL cipher suite configurationRun 'DISPLAY QMGR SSL' in runmqsc to view the queue manager's SSL configuration, or inspect the qm.ini file under the SSL stanza for CipherSuite settings.Affected if Cipher suites are configured using older or weaker algorithms (such as TLS 1.0, 3DES, or NULL encryption)
You are affected if your IBM WebSphere MQ installation is version 9.1.0.0, 9.1.0.1, or 9.1.1 and you have SSL/TLS channels configured with weak cryptographic algorithms.
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 dataUpdate IBM WebSphere MQ to a patched version that implements stronger cryptographic algorithms, and review/reconfigure TLS/SSL cipher suites and algorithm configurations to enforce modern cryptographic standards.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1925 — 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-2018-1925 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