# CVE-2023-31910: Memory corruption in n/a

> A heap-buffer-overflow in the Jerryscript parser allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** No
- **Published:** 10 May 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-433f-mxhm-43jr, UBUNTU-CVE-2023-31910

## What is CVE-2023-31910?

CVE-2023-31910 is a high-severity memory corruption vulnerability in Jerryscript Jerryscript, published on 10 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

Jerryscript 3.0 (commit 05dbbd1) was discovered to contain a heap-buffer-overflow via the component parser_parse_function_statement at /jerry-core/parser/js/js-parser-statm.c.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Jerryscript Jerryscript.

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

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

## Is CVE-2023-31910 being exploited?

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

## Other vulnerabilities in Jerryscript Jerryscript

- [CVE-2023-36109](https://insights.sbomify.com/CVE-2023-36109/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-38961](https://insights.sbomify.com/CVE-2023-38961/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-22597](https://insights.sbomify.com/CVE-2020-22597/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-42863](https://insights.sbomify.com/CVE-2021-42863/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-43453](https://insights.sbomify.com/CVE-2021-43453/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31910 is a high-severity memory corruption vulnerability in Jerryscript Jerryscript, published on 10 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-31910 exists.

Affected product: Jerryscript Jerryscript. 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-31910/ (Markdown: https://insights.sbomify.com/CVE-2023-31910/index.md)
```

## Sources

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

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