# CVE-2021-27025: Silent Configuration Failure in Puppet Agent

> Puppet Agent may suffer a Denial of Service condition or ignore Augeas settings before the first pluginsync, affecting configuration management reliability.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 18 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-27025, GHSA-q4g7-jrxv-67r9, RHSA-2022:8846, RHSA-2022:8862, UBUNTU-CVE-2021-27025

## What is CVE-2021-27025?

CVE-2021-27025 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 18 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable to a Denial of Service condition prior to the first 'pluginsync'.

## Which versions are affected by CVE-2021-27025?

4 open source packages ship an affected version, including puppet. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `puppet` | RubyGems | All versions | 6.25.1 |
| `puppet` | RubyGems | All versions | 6.25.1 |
| `puppet` | RubyGems | From 7.0.0 | 7.12.1 |
| `puppet` | RubyGems | From 7.0.0 | 7.12.1 |
| `puppet` | Red Hat:openstack:16.1::el8 | All versions | 0:5.5.10-14.el8ost |
| `puppet-headless` | Red Hat:openstack:16.1::el8 | All versions | 0:5.5.10-14.el8ost |
| `puppet-server` | Red Hat:openstack:16.1::el8 | All versions | 0:5.5.10-14.el8ost |
| `puppet` | Red Hat:openstack:16.2::el8 | All versions | 0:5.5.10-14.el8ost |
| `puppet-headless` | Red Hat:openstack:16.2::el8 | All versions | 0:5.5.10-14.el8ost |
| `puppet-server` | Red Hat:openstack:16.2::el8 | All versions | 0:5.5.10-14.el8ost |

Products: Fedoraproject Fedora, Puppet Puppet, Puppet Puppet Agent, Puppet Puppet Enterprise.

## How do I fix CVE-2021-27025?

Upgrade puppet to a fixed version for your release line: 6.25.1 or 7.12.1.

## Is CVE-2021-27025 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27025 and fix it if it is affected.

What it is: CVE-2021-27025 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 18 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27025 in the wild and no public exploit code.

Affected packages and fixed versions:
- puppet (RubyGems): affected all versions; fixed in 6.25.1
- puppet (RubyGems): affected all versions; fixed in 6.25.1
- puppet (RubyGems): affected from 7.0.0; fixed in 7.12.1
- puppet (RubyGems): affected from 7.0.0; fixed in 7.12.1

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-2021-27025/ (Markdown: https://insights.sbomify.com/CVE-2021-27025/index.md)
```

## Sources

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

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