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

> Attackers can read arbitrary files from the server via Local File Inclusion in Gibbon, exposing sensitive installation data.

- **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:** 29 Jun 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-mrqc-wm68-8hhj

## What is CVE-2023-34598?

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

### Official description

Gibbon v25.0.0 is vulnerable to a Local File Inclusion (LFI) where it's possible to include the content of several files present in the installation folder in the server's response.

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

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

It affects 1 product.


Products: Gibbonedu Gibbon.

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

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

## Is CVE-2023-34598 being exploited?

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

Public exploit code:

- Gibbon v25.0.0 is vulnerable to a Local File Inclusion (LFI) vulnerability where it's possible to include the content of several files present in the installation folder in the server's response. (github_poc): https://github.com/maddsec/CVE-2023-34598
- Gibbon本地文件包含漏洞（CVE-2023-34598） (github_poc): https://github.com/Lserein/CVE-2023-34598
- Gibbon v25.0.0 is vulnerable to a Local File Inclusion (LFI) (github_poc): https://github.com/Zer0F8th/CVE-2023-34598
- Gibbon v25.0.0 - Local File Inclusion (nuclei): http/cves/2023/CVE-2023-34598.yaml

## Other vulnerabilities in n/a

- [CVE-2024-24724](https://insights.sbomify.com/CVE-2024-24724/): Code injection in n/a (critical 9.8)
- [CVE-2023-45878](https://insights.sbomify.com/CVE-2023-45878/): File upload in n/a (critical 9.8)
- [CVE-2024-24725](https://insights.sbomify.com/CVE-2024-24725/): Deserialization in n/a (high 8.8)
- [CVE-2022-27305](https://insights.sbomify.com/CVE-2022-27305/): Auth bypass in n/a (high 8.8)
- [CVE-2023-45880](https://insights.sbomify.com/CVE-2023-45880/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34598 is a critical path traversal vulnerability in n/a, published on 29 Jun 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-34598 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-34598/ (Markdown: https://insights.sbomify.com/CVE-2023-34598/index.md)
```

## Sources

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

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