# CVE-2016-2788: Code injection in n/a

> Remote attackers can execute arbitrary code on MCollective servers via the mco ping command, requiring an upgrade to secure the system.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-2788, GHSA-v3fx-f8x7-f9vf

## What is CVE-2016-2788?

CVE-2016-2788 is a critical code injection vulnerability in Puppet Puppet Enterprise, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MCollective 2.7.0 and 2.8.x before 2.8.9, as used in Puppet Enterprise, allows remote attackers to execute arbitrary code via vectors related to the mco ping command.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-2788?

It affects 2 products.


Products: Puppet Marionette Collective, Puppet Puppet Enterprise.

## How do I fix CVE-2016-2788?

Upgrade to a fixed version.

## Is CVE-2016-2788 being exploited?

There is no known exploitation of CVE-2016-2788 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2788 and fix it if it is affected.

What it is: CVE-2016-2788 is a critical code injection vulnerability in Puppet Puppet Enterprise, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2788 in the wild and no public exploit code.

Affected product: Puppet Puppet Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-2788/ (Markdown: https://insights.sbomify.com/CVE-2016-2788/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2788
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2788
- OSV: https://osv.dev/vulnerability/CVE-2016-2788

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-2788/
Summaries are generated and may contain mistakes; the official description above is the record.