dbcve.org
Websphere MqApplication · Ibm

CVE-2018-1374

MEDIUM · 6.5 CVSS v3.0 Published 2018-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An IBM WebSphere MQ (Maintenance levels 7.1.0.0 - 7.1.0.9, 7.5.0.0 - 7.5.0.8, 8.0.0.0 - 8.0.0.8, 9.0.0.0 - 9.0.0.2, and 9.0.0 - 9.0.4) client connecting to a Queue Manager could cause a SIGSEGV in the Channel process amqrmppa. IBM X-Force ID: 137775.

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 confidence

A denial of service vulnerability in IBM WebSphere MQ's channel process (amqrmppa) allows a client connecting to a Queue Manager to trigger a SIGSEGV (segmentation fault), causing the channel to crash. The vulnerability affects versions 7.1.0.0 through 7.1.0.9, 7.5.0.0 through 7.5.0.8, 8.0.0.0 through 8.0.0.8, 9.0.0.0 through 9.0.0.2, and 9.0.0 through 9.0.4.

MitigationUpgrade IBM WebSphere MQ to a version beyond the affected maintenance ranges (9.0.0.3 or later for the 9.0.x branch, or the latest fix pack for 7.1, 7.5, and 8.0 branches). Test channel connectivity and message flow after upgrading to verify the fix.

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
Websphere MqApplication
Affected:= 7.1= 7.1.0.1= 7.1.0.2= 7.1.0.3= 7.1.0.4= 7.1.0.5= 7.1.0.6= 7.1.0.7= 7.1.0.8= 7.1.0.9= 7.5= 7.5.0.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check IBM WebSphere MQ installed version
    Run the command 'dspmqver -a' or 'dspmqver' to display version information. Alternatively, check the installation directory (typically $MQ_HOME) for version files or use 'lsrqmchk' for Queue Manager status.
    Affected if The installed version falls within 7.1.0.0-7.1.0.9, 7.5.0.0-7.5.0.8, 8.0.0.0-8.0.0.8, 9.0.0.0-9.0.0.2, or 9.0.0-9.0.4.
  2. Identify active Queue Managers
    Run 'dspmq' to list all Queue Managers and their status, or use 'runmqsc -m QMgrName' with 'display qmgr' to query specific Queue Manager details.
    Affected if Any Queue Manager is running on an affected version, as the channel process (amqrmppa) is active when a Queue Manager is operational.
  3. Check for channel process (amqrmppa) activity
    Use system commands like 'ps -ef | grep amqrmppa' on Unix/Linux or Task Manager/Process Explorer on Windows to see if the channel process is running.
    Affected if The channel process amqrmppa is running and the Queue Manager version is within the affected range.
  4. Review MQ error logs for crash evidence
    Examine MQ installation logs in the errors directory (for example, /var/mqm/errors or the MQ_DATA_PATH/errors folder) for FDC (Failure Diagnostic Center) files or amqrmppa-related crash logs containing SIGSEGV or segmentation fault entries.
    Affected if Recent crash logs show SIGSEGV in amqrmppa and the version matches the affected ranges.

You are affected if IBM WebSphere MQ version is 7.1.0.0 through 7.1.0.9, 7.5.0.0 through 7.5.0.8, 8.0.0.0 through 8.0.0.8, 9.0.0.0 through 9.0.0.2, or 9.0.0 through 9.0.4 and a Queue Manager with active channel process is running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade IBM WebSphere MQ to a version beyond the affected maintenance ranges (9.0.0.3 or later for the 9.0.x branch, or the latest fix pack for 7.1, 7.5, and 8.0 branches). Test channel connectivity and message flow after upgrading to verify the fix.

Fix this in Websphere Mq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1374 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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