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

> Attackers can exploit path traversal in BiblioCraft to write files anywhere, including the Minecraft mods folder, leading to arbitrary code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-q772-4845-474h

## What is CVE-2023-29478?

CVE-2023-29478 is a critical path traversal vulnerability in n/a, published on 7 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BiblioCraft before 2.4.6 does not sanitize path-traversal characters in filenames, allowing restricted write access to almost anywhere on the filesystem. This includes the Minecraft mods folder, which results in code execution.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Bibliocraftmod Bibliocraft.

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

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

## Is CVE-2023-29478 being exploited?

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

Public exploit code:

- CVE-2023-29478 - BiblioCraft File Manipulation/Remote Code Execution exploit affecting BiblioCraft versions prior to v2.4.6 (github_poc): https://github.com/Exopteron/BiblioRCE

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29478 is a critical path traversal vulnerability in n/a, published on 7 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29478 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-29478/ (Markdown: https://insights.sbomify.com/CVE-2023-29478/index.md)
```

## Sources

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

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