# CVE-2023-34204: Path traversal in n/a

> An attacker can overwrite files or modify cache by exploiting predictable temporary file paths in imapsync, potentially leading to privilege escalation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-pwpq-84p4-86mx

## What is CVE-2023-34204?

CVE-2023-34204 is a medium-severity path traversal vulnerability in n/a, published on 30 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

imapsync through 2.229 uses predictable paths under /tmp and /var/tmp in its default mode of operation. Both of these are typically world-writable, and thus (for example) an attacker can modify imapsync's cache and overwrite files belonging to the user who runs it.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2023-34204?

It affects 1 product.


Products: Imapsync Project Imapsync.

## How do I fix CVE-2023-34204?

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

## Is CVE-2023-34204 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4279](https://insights.sbomify.com/CVE-2013-4279/): Information disclosure in n/a (medium 5.0)
- [CVE-2014-2014](https://insights.sbomify.com/CVE-2014-2014/): Weak cryptography in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34204 and fix it if it is affected.

What it is: CVE-2023-34204 is a medium-severity path traversal vulnerability in n/a, published on 30 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34204 exists.

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

## Sources

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

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