dbcve.org
Websphere Mq LightApplication · Ibm

CVE-2015-4943

MEDIUM · 5.3 CVSS v3.0 Published 2016-01-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
IBM WebSphere MQ Light 1.x before 1.0.2 allows remote attackers to cause a denial of service (MQXR service crash) via a series of connect and disconnect actions, a different vulnerability than CVE-2015-4942.

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

IBM WebSphere MQ Light versions prior to 1.0.2 contain a denial of service vulnerability in the MQXR service. Remote attackers can crash the service by sending a series of connect and disconnect actions, indicating improper handling of connection state or resource management.

MitigationUpgrade to IBM WebSphere MQ Light version 1.0.2 or later to remediate this vulnerability.

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 Mq LightApplication
Affected:= 1.0= 1.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Verify IBM WebSphere MQ Light is installed
    Check for MQ Light installation by looking for the installation directory (typically /opt/mqlight or C:\Program Files\IBM\MQLight on Windows), or query installed packages on Linux (rpm -qa | grep -i mqlight or dpkg -l | grep -i mqlight)
    Affected if IBM WebSphere MQ Light is not installed on the system
  2. Determine installed MQ Light version
    Run 'mqlightversion' command if available, or check version files in the installation directory, or query the package manager for the installed version (rpm -qi mqlight or dpkg -s mqlight)
    Affected if Installed version is 1.0 or 1.0.0.1 (check against the affected range)
  3. Identify if MQXR service is configured or running
    Check for running MQXR service process (ps aux | grep -i mqxr on Linux, or check Windows services for MQXR service), or review MQ Light configuration files in the installation directory for MQXR service definition
    Affected if MQXR service is enabled or running on an affected version (1.0 or 1.0.0.1)

System is affected if IBM WebSphere MQ Light versions 1.0 or 1.0.0.1 are installed AND the MQXR service is enabled or running, as the denial of service vulnerability exists specifically in the MQXR service component.

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 to IBM WebSphere MQ Light version 1.0.2 or later to remediate this vulnerability.

Fix this in Websphere Mq Light Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4943 — 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-2015-4943 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