# CVE-2015-1029: Privilege escalation in n/a

> Authenticated attackers can escalate privileges or read sensitive data by prepopulating the fact cache in the Puppet stdlib module.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-44415, DEBIAN-CVE-2015-1029, GHSA-g3q8-3w6w-q3m9

## What is CVE-2015-1029?

CVE-2015-1029 is a medium-severity vulnerability in n/a, published on 16 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The puppetlabs-stdlib module 2.1 through 3.0 and 4.1.0 through 4.5.x before 4.5.1 for Puppet 2.8.8 and earlier allows remote authenticated users to gain privileges or obtain sensitive information by prepopulating the fact cache.

Weakness: CWE-264

## Which versions are affected by CVE-2015-1029?

It affects 1 product.


Products: Puppet Stdlib.

## How do I fix CVE-2015-1029?

Upgrade to a fixed version.

## Is CVE-2015-1029 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1029 and fix it if it is affected.

What it is: CVE-2015-1029 is a medium-severity vulnerability in n/a, published on 16 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1029 in the wild and no public exploit code.

Affected product: n/a. 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-2015-1029/ (Markdown: https://insights.sbomify.com/CVE-2015-1029/index.md)
```

## Sources

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

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