# CVE-2023-34878: Information disclosure in n/a

> Attackers can gain sensitive information via the dir parameter in the download-zip endpoint of Ujcms.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2023
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-mgj3-4cvf-j637

## What is CVE-2023-34878?

CVE-2023-34878 is a high-severity vulnerability in n/a, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Ujcms v6.0.2 allows attackers to gain sensitive information via the dir parameter to /api/backend/core/web-file-html/download-zip.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Ujcms Ujcms.

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

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

## Is CVE-2023-34878 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51350](https://insights.sbomify.com/CVE-2023-51350/): Code injection in n/a (critical 9.8)
- [CVE-2023-34747](https://insights.sbomify.com/CVE-2023-34747/): File upload in n/a (critical 9.8)
- [CVE-2023-34865](https://insights.sbomify.com/CVE-2023-34865/): Path traversal in n/a (critical 9.8)
- [CVE-2023-51806](https://insights.sbomify.com/CVE-2023-51806/): File upload in n/a (high 7.8)
- [CVE-2024-12483](https://insights.sbomify.com/CVE-2024-12483/): Dromara UJCMS User ID id authorization (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34878 is a high-severity vulnerability in n/a, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-34878 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-2023-34878/ (Markdown: https://insights.sbomify.com/CVE-2023-34878/index.md)
```

## Sources

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

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