# CVE-2022-45787: Apache James MIME4J: Temporary File Information Disclosure in MIME4J TempFileStorageProvider

> Local attackers can read sensitive data from temporary files due to lax permissions in the Apache James MIME4J library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-q84x-3476-8ff2, OESA-2025-2296, OESA-2025-2343, OESA-2025-2344, OESA-2025-2345, OESA-2025-2346, OESA-2025-2347

## What is CVE-2022-45787?

CVE-2022-45787 is a medium-severity vulnerability in Apache James MIME4J, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unproper laxist permissions on the temporary files used by MIME4J TempFileStorageProvider may lead to information disclosure to other local users. This issue affects Apache James MIME4J version 0.8.8 and prior versions.

We recommend users to upgrade to MIME4j version 0.8.9 or later.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2022-45787?

2 open source packages ship an affected version, including org.apache.james:apache-mime4j-storage. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.james:apache-mime4j-storage` | Maven | All versions | 0.8.9 |
| `org.apache.james:apache-mime4j-storage` | Maven | All versions | 0.8.9 |

Products: Apache James.

## How do I fix CVE-2022-45787?

Upgrade org.apache.james:apache-mime4j-storage to 0.8.9 or later.

## Is CVE-2022-45787 being exploited?

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

## Other vulnerabilities in Apache James MIME4J

- [CVE-2023-51518](https://insights.sbomify.com/CVE-2023-51518/): Apache James server: Privilege escalation via JMX pre-authentication deserialisation (critical 9.8)
- [CVE-2019-0228](https://insights.sbomify.com/CVE-2019-0228/): Vulnerability that affects org.apache.pdfbox:pdfbox (critical 9.8)
- [CVE-2021-40525](https://insights.sbomify.com/CVE-2021-40525/): Sieve file storage vulnerable to path traversal attacks (critical 9.1)
- [CVE-2023-26269](https://insights.sbomify.com/CVE-2023-26269/): Apache James server: Privilege escalation through unauthenticated JMX (high 7.8)
- [CVE-2006-2806](https://insights.sbomify.com/CVE-2006-2806/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45787 and fix it if it is affected.

What it is: CVE-2022-45787 is a medium-severity vulnerability in Apache James MIME4J, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45787 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.james:apache-mime4j-storage (Maven): affected all versions; fixed in 0.8.9
- org.apache.james:apache-mime4j-storage (Maven): affected all versions; fixed in 0.8.9

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-2022-45787/ (Markdown: https://insights.sbomify.com/CVE-2022-45787/index.md)
```

## Sources

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

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