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

> Attackers can track email recipients by forcing remote resource loading during printing, potentially revealing user activity and IP addresses.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 29 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-43wr-9394-fxp2

## What is CVE-2023-24597?

CVE-2023-24597 is a medium-severity vulnerability in n/a, published on 29 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OX App Suite before frontend 7.10.6-rev24 allows the loading (without user consent) of an e-mail message's remote resources during printing.

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

It affects 1 product.


Products: Open-Xchange Ox App Suite.

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

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

## Is CVE-2023-24597 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29851](https://insights.sbomify.com/CVE-2022-29851/): Command injection in n/a (critical 9.8)
- [CVE-2022-23100](https://insights.sbomify.com/CVE-2022-23100/): Command injection in n/a (critical 9.8)
- [CVE-2022-24405](https://insights.sbomify.com/CVE-2022-24405/): Command injection in n/a (critical 9.8)
- [CVE-2023-29048](https://insights.sbomify.com/CVE-2023-29048/): Command injection in OX App Suite (high 8.8)
- [CVE-2023-29051](https://insights.sbomify.com/CVE-2023-29051/): Missing authorization in OX App Suite (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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