# CVE-2022-25350: Command Injection in puppet-facter

> Attackers can execute arbitrary commands via the getFact function in the puppet-facter library due to improper input sanitization.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2023
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-g5qr-xgg7-8q2w

## What is CVE-2022-25350?

CVE-2022-25350 is a high-severity command injection vulnerability in puppet-facter, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

All versions of the package puppet-facter are vulnerable to Command Injection via the getFact  function due to improper input sanitization.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2022-25350?

2 open source packages ship an affected version, including puppet-facter. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `puppet-facter` | npm | All versions to 0.0.2 | None |
| `puppet-facter` | npm | All versions to 0.0.2 | None |

Products: Helecloud Puppet-Facter.

## How do I fix CVE-2022-25350?

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

## Is CVE-2022-25350 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25350 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25350 and fix it if it is affected.

What it is: CVE-2022-25350 is a high-severity command injection vulnerability in puppet-facter, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25350 exists.

Affected packages and fixed versions:
- puppet-facter (npm): affected all versions up to 0.0.2; no fix listed
- puppet-facter (npm): affected all versions up to 0.0.2; no fix listed

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

## Sources

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

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