# CVE-2022-42717: Privilege escalation in n/a

> Non-privileged users can execute arbitrary commands as root if the host uses the insecure recommended sudoers configuration for Vagrant.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Oct 2022
- **Updated:** 20 May 2025
- **Also known as:** AZL-11115, GHSA-mc87-5qgf-5qvj, UBUNTU-CVE-2022-42717

## What is CVE-2022-42717?

CVE-2022-42717 is a high-severity vulnerability in n/a, published on 11 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Hashicorp Packer before 2.3.1. The recommended sudoers configuration for Vagrant on Linux is insecure. If the host has been configured according to this documentation, non-privileged users on the host can leverage a wildcard in the sudoers configuration to execute arbitrary commands as root.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Hashicorp Vagrant.

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

Change a configuration setting.

## Is CVE-2022-42717 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16777](https://insights.sbomify.com/CVE-2017-16777/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-16001](https://insights.sbomify.com/CVE-2017-16001/): Race condition in n/a (high 7.8)
- [CVE-2023-5834](https://insights.sbomify.com/CVE-2023-5834/): Vagrant’s Windows Installer Allowed Directory Junction Write (low 3.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42717 is a high-severity vulnerability in n/a, published on 11 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-42717 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-42717/ (Markdown: https://insights.sbomify.com/CVE-2022-42717/index.md)
```

## Sources

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

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