# CVE-2022-29583: Path traversal in n/a

> An attacker could potentially execute arbitrary code by exploiting unquoted service paths in the kardianos Go service package on Windows.

- **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:** No
- **Published:** 22 Apr 2022
- **Updated:** 3 Aug 2024

## What is CVE-2022-29583?

CVE-2022-29583 is a high-severity path traversal vulnerability in n/a, published on 22 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

service_windows.go in the kardianos service package for Go omits quoting that is sometimes needed for execution of a Windows service executable from the intended directory. NOTE: this finding could not be reproduced by its original reporter or by others.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Service Project Service.

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

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

## Is CVE-2022-29583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29583 is a high-severity path traversal vulnerability in n/a, published on 22 Apr 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-29583 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-29583/ (Markdown: https://insights.sbomify.com/CVE-2022-29583/index.md)
```

## Sources

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

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