# CVE-2024-32477: Race condition when flushing input stream leads to permission prompt bypass

> Attackers can bypass Deno permission prompts via a race condition involving ANSI escape sequences, allowing unauthorized execution of unsafe actions.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-95cj-3hr2-7j5j, JLSEC-2026-106

## What is CVE-2024-32477?

CVE-2024-32477 is a high-severity vulnerability in denoland deno, published on 18 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Deno is a JavaScript, TypeScript, and WebAssembly runtime with secure defaults. By using ANSI escape sequences and a race between `libc::tcflush(0, libc::TCIFLUSH)` and reading standard input, it's possible to manipulate the permission prompt and force it to allow an unsafe action regardless of the user input. Some ANSI escape sequences act as a info request to the master terminal emulator and the terminal emulator sends back the reply in the PTY channel. standard streams also use this channel to send and get data. For example the `\033[6n` sequence requests the current cursor position. These sequences allow us to append data to the standard input of Deno. This vulnerability allows an attacker to bypass Deno permission policy.  This vulnerability is fixed in 1.42.2.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: Deno Deno.

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

Upgrade to a fixed version.

## Is CVE-2024-32477 being exploited?

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

## Other vulnerabilities in denoland deno

- [CVE-2023-28445](https://insights.sbomify.com/CVE-2023-28445/): Deno improperly handles resizable ArrayBuffer (critical 10.0)
- [CVE-2022-24783](https://insights.sbomify.com/CVE-2022-24783/): Sandbox bypass leading to arbitrary code execution in Deno (critical 10.0)
- [CVE-2021-32619](https://insights.sbomify.com/CVE-2021-32619/): Static imports inside dynamically imported modules do not adhere to permission checks (critical 9.8)
- [CVE-2026-22863](https://insights.sbomify.com/CVE-2026-22863/): Deno node:crypto doesn't finalize cipher (critical 9.2)
- [CVE-2024-27936](https://insights.sbomify.com/CVE-2024-27936/): Deno interactive permission prompt spoofing via improper ANSI stripping (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32477 is a high-severity vulnerability in denoland deno, published on 18 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32477 exists.

Affected product: denoland deno. 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-32477/ (Markdown: https://insights.sbomify.com/CVE-2024-32477/index.md)
```

## Sources

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

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