# CVE-2021-27205: Information disclosure in n/a

> An attacker with local access can read sensitive self-destructed messages stored in the application's sandbox directory on macOS.

- **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:** No
- **Published:** 12 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-g3fx-gvwr-w892

## What is CVE-2021-27205?

CVE-2021-27205 is a medium-severity vulnerability in n/a, published on 12 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Telegram before 7.4 (212543) Stable on macOS stores the local copy of self-destructed messages in a sandbox path, leading to sensitive information disclosure.

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

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

It affects 1 product.


Products: Telegram Telegram.

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

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

## Is CVE-2021-27205 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10044](https://insights.sbomify.com/CVE-2019-10044/): Other in n/a (high 8.8)
- [CVE-2018-20436](https://insights.sbomify.com/CVE-2018-20436/): Server-side request forgery in n/a (high 8.1)
- [CVE-2024-7014](https://insights.sbomify.com/CVE-2024-7014/): Improper multimedia file attachment validation in Telegram for Android app (high 7.1)
- [CVE-2021-31320](https://insights.sbomify.com/CVE-2021-31320/): Memory corruption in n/a (high 7.1)
- [CVE-2021-31321](https://insights.sbomify.com/CVE-2021-31321/): Memory corruption in n/a (high 7.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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