LiveActive security incident?Get immediate response
CVE Record

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

IBM MQ 7.1.0.0 - 7.1.0.9, 7.5.0.0 - 7.5.0.9, 8.0.0.0 - 8.0.0.11, 9.0.0.0 - 9.0.0.6, 9.1.0.0 - 9.1.0.2, and 9.1.1 - 9.1.2 is vulnerable to a denial of service attack caused by a memory leak in the clustering code. IBM X-Force ID: 158337.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-4141 is a denial-of-service issue in IBM MQ clustering code. A memory leak can exhaust resources and disrupt MQ availability. The business risk is service interruption for systems depending on clustered IBM MQ, not data theft or code execution based on the supplied sources.

Executive priority

Treat as a targeted availability risk. It is not marked critical and no active exploitation is cited, but clustered MQ often supports important transaction flows, so remediation should follow normal patch governance with priority for production clusters.

Technical view

IBM MQ versions 7.1.0.0-7.1.0.9, 7.5.0.0-7.5.0.9, 8.0.0.0-8.0.0.11, 9.0.0.0-9.0.0.6, 9.1.0.0-9.1.0.2, and 9.1.1-9.1.2 contain a clustering-code memory leak. CVSS 3.0 is 5.3 with network attack vector, high complexity, low privileges, and high availability impact.

Likely exposure

Exposure is most likely where affected IBM MQ versions are deployed with clustering functionality in use, especially where MQ network services are reachable by users or systems with low-level access. Non-clustered deployments may be less exposed, but the provided sources do not define exact trigger conditions.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. CVSS metadata indicates exploit maturity was unproven. Exploitation requires network access, low privileges, and high attack complexity, but successful exploitation can affect availability.

Researcher notes

No CWE is listed in the supplied data. The CVSS vector is availability-only with no confidentiality or integrity impact. Sources do not provide exploit mechanics, precise trigger conditions, or detailed mitigations beyond IBM advisory references and official-remediation metadata.

Mitigation direction

  • Review IBM advisory 876772 and apply the specified IBM MQ fix pack or upgrade.
  • Prioritize clustered IBM MQ queue managers in affected version ranges.
  • Restrict network access to MQ services to trusted systems and administrators.
  • Monitor MQ process memory and availability until remediation is complete.
  • Confirm unsupported IBM MQ versions are removed or upgraded.

Validation and detection

  • Inventory IBM MQ versions across all queue managers.
  • Identify queue managers using IBM MQ clustering.
  • Compare installed versions against the affected ranges in the CVE record.
  • Check IBM advisory 876772 for the fixed target level.
  • Review monitoring for abnormal MQ memory growth or availability incidents.
Prepared
Confidence
high
Sources
4

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-4141 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/UI:N/S:U/I:N/A:H/C:N/AV:N/AC:H/PR:L/RC:C/E:U/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/UI:N/S:U/I:N/A:H/C:N/AV:N/AC:H/PR:L/RC:C/E:U/RL:O1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/UI:N/S:U/I:N/A:H/C:N/AV:N/AC:H/PR:L/RC:C/E:U/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.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.9Listed
Weakness

CWE details

No CWE listed

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