# CVE-2020-1915: Out-of-bounds Read in Facebook Hermes

> Attackers can cause denial of service or memory corruption in Hermes JavaScript engine via crafted scripts if untrusted code evaluation is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x4cf-6jr3-3qvp

## What is CVE-2020-1915?

CVE-2020-1915 is a high-severity memory corruption vulnerability in Facebook Hermes, published on 26 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An out-of-bounds read in the JavaScript Interpreter in Facebook Hermes prior to commit 8cb935cd3b2321c46aa6b7ed8454d95c75a7fca0 allows attackers to cause a denial of service attack or possible further memory corruption via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits evaluation of untrusted JavaScript. Hence, most React Native applications are not affected.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-1915?

2 open source packages ship an affected version, including hermes-engine. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hermes-engine` | npm | All versions | 0.7.2 |
| `hermes-engine` | npm | All versions | 0.7.2 |

Products: Facebook Hermes.

## How do I fix CVE-2020-1915?

Upgrade hermes-engine to 0.7.2 or later.

## Is CVE-2020-1915 being exploited?

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

## Other vulnerabilities in Facebook Hermes

- [CVE-2023-23556](https://insights.sbomify.com/CVE-2023-23556/): Memory corruption in Hermes (critical 9.8)
- [CVE-2023-23557](https://insights.sbomify.com/CVE-2023-23557/): Memory corruption in Hermes (critical 9.8)
- [CVE-2023-25933](https://insights.sbomify.com/CVE-2023-25933/): Memory corruption in Hermes (critical 9.8)
- [CVE-2023-28081](https://insights.sbomify.com/CVE-2023-28081/): Use after free in Hermes (critical 9.8)
- [CVE-2023-30470](https://insights.sbomify.com/CVE-2023-30470/): Use after free in Hermes (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1915 and fix it if it is affected.

What it is: CVE-2020-1915 is a high-severity memory corruption vulnerability in Facebook Hermes, published on 26 Oct 2020. 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-2020-1915 in the wild and no public exploit code.

Affected packages and fixed versions:
- hermes-engine (npm): affected all versions; fixed in 0.7.2
- hermes-engine (npm): affected all versions; fixed in 0.7.2

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-2020-1915/ (Markdown: https://insights.sbomify.com/CVE-2020-1915/index.md)
```

## Sources

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

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