dbcve.org
Mcollective Puppet AgentApplication · Puppetlabs

CVE-2015-7331

MEDIUM · 6.6 CVSS v3.0 Published 2017-01-30
Fix available
A fix is available. Upgrade to after 1.11.0 or later.
See remediation →
72/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
The mcollective-puppet-agent plugin before 1.11.1 for Puppet allows remote attackers to execute arbitrary code via vectors involving the --server argument.

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

The mcollective-puppet-agent plugin before version 1.11.1 contains a command injection vulnerability where the --server argument is not properly sanitized before being passed to system calls, allowing remote attackers to execute arbitrary code.

MitigationUpgrade the mcollective-puppet-agent plugin to version 1.11.1 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
Mcollective Puppet AgentApplication
Affected:<= 1.11.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
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:L/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 mcollective-puppet-agent installation
    Run `mco plugin package mcollective-puppet-agent` or check the installed package manager for the mcollective-puppet-agent package (e.g., `rpm -q mcollective-puppet-agent` or `dpkg -l | grep mcollective-puppet-agent`)
    Affected if The package is installed and returns a version number of 1.11.0 or lower
  2. Verify the vulnerable version
    Compare the installed version number against the affected range: versions 1.11.0 and earlier are vulnerable
    Affected if The installed version is 1.11.0 or any earlier version (e.g., 1.10.0, 1.9.0, etc.)
  3. Confirm the --server argument is in use
    Inspect the MCollective client configuration or any automation scripts that invoke the puppet agent with the `--server` argument (commonly found in /etc/mcollective/client.cfg, /etc/mcollective/server.cfg, or related Puppet/MCollective configuration files)
    Affected if The --server argument is configured and passed to the mcollective-puppet-agent plugin

The environment is affected if mcollective-puppet-agent version 1.11.0 or earlier is installed and the --server argument is being used in configurations or scripts.

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
Upgrade available Upgrade to a release after 1.11.0
Interim mitigation

Upgrade the mcollective-puppet-agent plugin to version 1.11.1 or later to remediate this vulnerability.

Fix this in Mcollective Puppet Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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