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

> Akka HTTP creates temporary files with weak permissions during uploads, allowing local attackers to read sensitive data.

- **Severity:** Medium 4.7 (`CVSS:3.1/AC:H/AV:L/A:N/C:H/I:N/PR:L/S:U/UI: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:** No
- **Published:** 21 May 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-9f9g-qwcw-j94j

## What is CVE-2023-33251?

CVE-2023-33251 is a medium-severity vulnerability in n/a, published on 21 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When Akka HTTP before 10.5.2 accepts file uploads via the FileUploadDirectives.fileUploadAll directive, the temporary file it creates has too weak permissions: it is readable by other users on Linux or UNIX, a similar issue to CVE-2022-41946.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Lightbend Akka Http.

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

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

## Is CVE-2023-33251 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16131](https://insights.sbomify.com/CVE-2018-16131/): High severity vulnerability that affects com.typesafe.akka:akka-http-core_2.11 and com.typesafe.akka:akka-http-core_2.12 (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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