# CVE-2018-6512: Code injection in Puppet Enterprise 2018.1.x prior to 2018.1.1, razor-server and pe-razor-server prior to 1.9.0.0

> Attackers can execute arbitrary code during the upgrade of pe-razor-server in Puppet Enterprise, 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:** No
- **Published:** 11 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7mp2-f3vh-j4w4

## What is CVE-2018-6512?

CVE-2018-6512 is a critical code injection vulnerability in Puppet Puppet Enterprise, published on 11 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The previous version of Puppet Enterprise 2018.1 is vulnerable to unsafe code execution when upgrading pe-razor-server. Affected releases are Puppet Enterprise: 2018.1.x versions prior to 2018.1.1 and razor-server and pe-razor-server prior to 1.9.0.0.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2018-6512?

It affects 3 products.


Products: Puppet Pe-Razor-Server, Puppet Puppet Enterprise, Puppet Razor-Server.

## How do I fix CVE-2018-6512?

No fix has been published for CVE-2018-6512 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-6512 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6512 and fix it if it is affected.

What it is: CVE-2018-6512 is a critical code injection vulnerability in Puppet Puppet Enterprise, published on 11 Jun 2018. 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-2018-6512 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-2018-6512/ (Markdown: https://insights.sbomify.com/CVE-2018-6512/index.md)
```

## Sources

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

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