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

> Attackers can access internal JSP and XML files in Zimbra Collaboration Suite, potentially exposing sensitive configuration or source code data.

- **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:** 31 Jul 2023
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-g769-wj2j-6j53

## What is CVE-2023-38750?

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

### Official description

In Zimbra Collaboration (ZCS) 8 before 8.8.15 Patch 41, 9 before 9.0.0 Patch 34, and 10 before 10.0.2, internal JSP and XML files can be exposed.

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

It affects 1 product.


Products: Zimbra Zimbra.

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

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

## Is CVE-2023-38750 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-9665](https://insights.sbomify.com/CVE-2024-9665/): Zimbra GraphQL Cross-Site Request Forgery Information Disclosure Vulnerability (medium 6.5)
- [CVE-2020-11737](https://insights.sbomify.com/CVE-2020-11737/): Cross-site scripting in Zimbra (medium 6.1)
- [CVE-2013-1938](https://insights.sbomify.com/CVE-2013-1938/): Zimbra 2013 has XSS in aspell.php (medium 6.1)
- [CVE-2012-1213](https://insights.sbomify.com/CVE-2012-1213/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38750 is a high-severity vulnerability in n/a, published on 31 Jul 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-38750 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-38750/ (Markdown: https://insights.sbomify.com/CVE-2023-38750/index.md)
```

## Sources

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

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