# CVE-2022-45301: Misconfiguration in n/a

> Insecure file permissions in the Chocolatey Ruby package allow authenticated users to modify files, potentially leading to privilege escalation or code execution.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-jmhx-fqfh-838h

## What is CVE-2022-45301?

CVE-2022-45301 is a medium-severity vulnerability in n/a, published on 29 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure permissions in Chocolatey Ruby package v3.1.2.1 and below grants all users in the Authenticated Users group write privileges for the path C:\tools\ruby31 and all files located in that folder.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Chocolatey Chocolatey Ruby.

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

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

## Is CVE-2022-45301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45301 is a medium-severity vulnerability in n/a, published on 29 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45301 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-2022-45301/ (Markdown: https://insights.sbomify.com/CVE-2022-45301/index.md)
```

## Sources

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

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