dbcve.org
CheckmkApplication

CVE-2024-3367

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Argument injection in websphere_mq agent plugin in Checkmk 2.0.0, 2.1.0, <2.2.0p26 and <2.3.0b5 allows local attacker to inject one argument to runmqsc

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 local argument injection vulnerability exists in the WebSphere MQ (websphere_mq) agent plugin of Checkmk versions 2.0.0, 2.1.0, <2.2.0p26 and <2.3.0b5. A local attacker with access to the system where the Checkmk agent runs can inject an additional argument into the runmqsc command, potentially allowing manipulation of IBM WebSphere MQ operations.

MitigationUpgrade Checkmk to version 2.2.0p26, 2.3.0b5 or later. As a compensating control, restrict local access to the Checkmk agent configuration and monitor agent plugin execution for unauthorized arguments.

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
CheckmkApplication
Affected:<= 2.0.0= 2.1.0= 2.2.0= 2.3.0

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify installed Checkmk version
    Run 'cmk --version' or check '/opt/omd/sites/*/etc/version' to determine the exact Checkmk version installed
    Affected if Version is 2.0.0, 2.1.0, 2.2.0, 2.3.0, or any version lower than 2.2.0p26 or 2.3.0b5
  2. Locate the websphere_mq agent plugin
    Search for the websphere_mq plugin file in the Checkmk agent plugins directory, typically found under /opt/omd/sites/*/lib/check_mk_agent/plugins/ or /usr/lib/check_mk_agent/plugins/
    Affected if The websphere_mq plugin file exists on the system
  3. Verify websphere_mq plugin configuration
    Check for websphere_mq configuration files in the agent configuration directory, commonly under /opt/omd/sites/*/etc/check_mk/ or /etc/check_mk/
    Affected if A configuration file for websphere_mq exists and defines queue manager parameters, indicating the plugin is configured for use
  4. Inspect plugin file permissions
    Run 'ls -la' on the websphere_mq plugin file and its configuration directory to determine which local users have read or write access
    Affected if Non-privileged users or multiple local users have write access to the agent plugin or its configuration files
  5. Review agent execution context
    Examine how the websphere_mq plugin is invoked and check if it runs with elevated privileges or accesses IBM WebSphere MQ binaries (runmqsc)
    Affected if The plugin executes runmqsc commands and runs with permissions that allow interaction with queue managers

A system is affected if it runs any Checkmk version below 2.2.0p26 or 2.3.0b5, has the websphere_mq agent plugin installed and configured, and local attackers could manipulate plugin configuration or parameters passed to runmqsc commands.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.0
Interim mitigation

Upgrade Checkmk to version 2.2.0p26, 2.3.0b5 or later. As a compensating control, restrict local access to the Checkmk agent configuration and monitor agent plugin execution for unauthorized arguments.

Recommended fix High confidence

Upgrade to Checkmk 2.2.0p26 or later, or to the latest stable branch (2.3.0/2.4.0)

  1. 1. Identify the currently installed Checkmk version using 'cmk --version' or the web interface
  2. 2. For Checkmk 2.0.x and 2.1.x users: Plan upgrade to a supported stable branch (2.2.0p26 or later, or 2.3.0/2.4.0)
  3. 3. For Checkmk 2.2.0 users: Upgrade to version 2.2.0p26 or later within the 2.2.x branch
  4. 4. For Checkmk 2.3.0 beta users: Upgrade to the stable 2.3.0 release or later
  5. 5. Before upgrading, review the Checkmk upgrade documentation and take a backup of the site
  6. 6. Perform the upgrade using 'cmk -U' or the web-based update mechanism
  7. 7. After upgrade, verify the websphere_mq plugin is updated and test that it functions correctly
Caveat Checkmk major version upgrades may require site migration and can have configuration changes; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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