# CVE-2021-3394: Privilege escalation in n/a

> Insecure folder permissions in Millennium Millewin allow local attackers to escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m2vv-94mg-crph

## What is CVE-2021-3394?

CVE-2021-3394 is a high-severity vulnerability in n/a, published on 9 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Millennium Millewin (also known as "Cartella clinica") 13.39.028, 13.39.28.3342, and 13.39.146.1 has insecure folder permissions allowing a malicious user for a local privilege escalation.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2021-3394?

It affects 1 product.


Products: Millewin Millewin.

## How do I fix CVE-2021-3394?

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

## Is CVE-2021-3394 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3394 exists.

Public exploit code:

- Millewin 13.39.146.1 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3394 and fix it if it is affected.

What it is: CVE-2021-3394 is a high-severity vulnerability in n/a, published on 9 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3394 exists.

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

## Sources

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

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