# CVE-2023-31669: Denial of service in n/a

> Attackers can cause a crash in the wat2wasm tool by using specific input characters, leading to denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 May 2023
- **Updated:** 31 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-31669, GHSA-24pv-x5f7-pv4r, UBUNTU-CVE-2023-31669

## What is CVE-2023-31669?

CVE-2023-31669 is a medium-severity denial of service vulnerability in n/a, published on 23 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

WebAssembly wat2wasm v1.0.32 allows attackers to cause a libc++abi.dylib crash by putting '@' before a quote (").

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2023-31669?

It affects 1 product.


Products: Webassembly Webassembly Binary Toolkit.

## How do I fix CVE-2023-31669?

Upgrade to a fixed version.

## Is CVE-2023-31669 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31670](https://insights.sbomify.com/CVE-2023-31670/): Denial of service in n/a (high 7.5)
- [CVE-2023-46331](https://insights.sbomify.com/CVE-2023-46331/): Memory corruption in n/a (medium 5.5)
- [CVE-2023-46332](https://insights.sbomify.com/CVE-2023-46332/): Memory corruption in n/a (medium 5.5)
- [CVE-2025-3122](https://insights.sbomify.com/CVE-2025-3122/): WebAssembly wabt binary-reader-interp.cc BeginFunctionBody null pointer dereference (low 2.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31669 and fix it if it is affected.

What it is: CVE-2023-31669 is a medium-severity denial of service vulnerability in n/a, published on 23 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31669 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-2023-31669/ (Markdown: https://insights.sbomify.com/CVE-2023-31669/index.md)
```

## Sources

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

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