# CVE-2024-36052: Other in n/a

> Attackers can spoof screen output in WinRAR via ANSI escape sequences, potentially misleading users about file contents or status.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-gp37-m2c5-j775

## What is CVE-2024-36052?

CVE-2024-36052 is a high-severity vulnerability in n/a, published on 21 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RARLAB WinRAR before 7.00, on Windows, allows attackers to spoof the screen output via ANSI escape sequences, a different issue than CVE-2024-33899.

Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences)

## Which versions are affected by CVE-2024-36052?

It affects 1 product.


Products: Rarlab Winrar.

## How do I fix CVE-2024-36052?

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

## Is CVE-2024-36052 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-6218](https://insights.sbomify.com/CVE-2025-6218/): RARLAB WinRAR Path Traversal (high 7.8, exploited in the wild)
- [CVE-2023-38831](https://insights.sbomify.com/CVE-2023-38831/): RARLAB WinRAR Code Execution (high 7.8, exploited in the wild)
- [CVE-2018-20250](https://insights.sbomify.com/CVE-2018-20250/): WinRAR Absolute Path Traversal (high 7.8, exploited in the wild)
- [CVE-2008-7144](https://insights.sbomify.com/CVE-2008-7144/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1254](https://insights.sbomify.com/CVE-2004-1254/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36052 and fix it if it is affected.

What it is: CVE-2024-36052 is a high-severity vulnerability in n/a, published on 21 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36052 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-2024-36052/ (Markdown: https://insights.sbomify.com/CVE-2024-36052/index.md)
```

## Sources

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

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