# CVE-2024-32669: Possible stack overflow due to a string encoding processing error

> A stack overflow in the escargot JavaScript engine test code could cause a denial of service, though it does not affect released versions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7g2q-cf23-xvj2

## What is CVE-2024-32669?

CVE-2024-32669 is a medium-severity memory corruption vulnerability in Samsung Open Source Escargot, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Input Validation vulnerability in Samsung Open Source escargot JavaScript engine allows Overflow Buffers.
However, it occurs in the test code and does not include in the release.

This issue affects escargot: 4.0.0.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2024-32669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32669 is a medium-severity memory corruption vulnerability in Samsung Open Source Escargot, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32669 in the wild and no public exploit code.

Affected product: Samsung Open Source Escargot. 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-32669/ (Markdown: https://insights.sbomify.com/CVE-2024-32669/index.md)
```

## Sources

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

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