LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4378: IBM MQ 7.5.0.0 - 7.5.0.9, 7.1.0.0 - 7.1.0.9, 8.0.0.0 - 8.0.0.12, 9.0.0.0 - 9.0.0.6, 9.1.0.0 - 9.1.0.2, and...

IBM MQ 7.5.0.0 - 7.5.0.9, 7.1.0.0 - 7.1.0.9, 8.0.0.0 - 8.0.0.12, 9.0.0.0 - 9.0.0.6, 9.1.0.0 - 9.1.0.2, and 9.1.0 - 9.1.2 command server is vulnerable to a denial of service attack caused by an authenticated and authorized user using specially crafted PCF messages. IBM X-Force ID: 162084.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let a legitimate, authorized IBM MQ user disrupt MQ command server availability. It is not described as data theft or system takeover. Business urgency depends on whether affected IBM MQ versions are still running and whether untrusted or broadly provisioned users can access MQ administrative messaging paths.

Executive priority

Treat as a moderate availability risk. Prioritize remediation for business-critical MQ systems, internet-adjacent management paths, or environments where many users or applications have MQ administrative privileges.

Technical view

CVE-2019-4378 affects IBM MQ command server versions 7.1.0.0-7.1.0.9, 7.5.0.0-7.5.0.9, 8.0.0.0-8.0.0.12, 9.0.0.0-9.0.0.6, and 9.1.0.0-9.1.0.2 / 9.1.0-9.1.2. An authenticated, authorized user can cause denial of service using specially crafted PCF messages.

Likely exposure

Exposure is most likely in environments still running the listed IBM MQ maintenance levels, especially where MQ command server access or PCF-capable administrative permissions are granted broadly to users, applications, or service accounts.

Exploitation context

The provided sources do not indicate CISA KEV listing or active exploitation. The CVSS data indicates network reachability, low privileges, no user interaction, high attack complexity, and high availability impact without confidentiality or integrity impact.

Researcher notes

The public bundle provides affected ranges, impact type, prerequisite access, and CVSS context, but not detailed crash conditions or fixed version numbers. Avoid assuming exploit availability or mitigation specifics beyond IBM guidance.

Mitigation direction

  • Check IBM’s advisory for the supported fixed maintenance level or interim fix.
  • Upgrade affected IBM MQ installations according to IBM guidance.
  • Restrict MQ administrative and PCF-message privileges to trusted accounts only.
  • Review service accounts with command server access and remove unnecessary permissions.
  • Monitor command server health and abnormal MQ availability events.

Validation and detection

  • Inventory IBM MQ versions across production, staging, and disaster recovery systems.
  • Compare installed versions against the affected ranges in the CVE description.
  • Identify queue managers where the command server is enabled and reachable.
  • Review MQ authorities for users or applications allowed to submit administrative PCF messages.
  • Check operational logs for unexplained command server failures or MQ availability incidents.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-4378 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/C:N/A:H/AC:H/S:U/UI:N/AV:N/I:N/PR:L/E:U/RC:C/RL:O

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.0MediumCVSS:3.0/C:N/A:H/AC:H/S:U/UI:N/AV:N/I:N/PR:L/E:U/RC:C/RL:O1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.3Medium
CVSS 3.0 vector shape for CVE-2019-4378Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/C:N/A:H/AC:H/S:U/UI:N/AV:N/I:N/PR:L/E:U/RC:C/RL:O

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMMQ9.0.0.1, 8.0.0.1, 8.0.0.2, 8.0.0.3, 8.0.0.4, 8.0.0.5, 8.0.0.6, 8.0.0.7, 9.0.0.2, 7.5.0.1, 7.5.0.2, 7.5.0.3, 7.5.0.4, 7.5.0.5, 7.5.0.6, 7.5.0.7, 7.5.0.8, 8.0.0.8, 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, 8.0.0.9, 9.0.0.3, 8.0.0.0, 8.0.0.10, 9.0.0.0, 9.0.0.4, 9.0.0.5, 9.1.0.0, 9.1.0.1, 9.1.1, 9.1.0.2, 9.1.2, 8.0.0.11, 9.0.0.6, 7.1.0.0, 7.1.0.8, 7.1.0.9, 7.5.0.0, 7.5.0.9, 8.0.0.12Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.