# CVE-2021-44512: Misconfiguration in n/a

> Local attackers can compromise session integrity or steal session IDs due to world-writable permissions on the tmate sessions directory.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-44512, GHSA-mpgw-pwqr-q9jp, UBUNTU-CVE-2021-44512

## What is CVE-2021-44512?

CVE-2021-44512 is a high-severity vulnerability in n/a, published on 7 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

World-writable permissions on the /tmp/tmate/sessions directory in tmate-ssh-server 2.3.0 allow a local attacker to compromise the integrity of session handling, or obtain the read-write session ID from a read-only session symlink in this directory.

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

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

It affects 1 product.


Products: Tmate Tmate-Ssh-Server.

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

Apply the vendor's patch.

## Is CVE-2021-44512 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44513](https://insights.sbomify.com/CVE-2021-44513/): Race condition in n/a (high 7.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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