# CVE-2020-6836: Command Injection in hot-formula-parser

> Attackers can execute arbitrary code on the server by injecting malicious formulas into the hot-formula-parser package due to unsanitized input in eval calls.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 11 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rc77-xxq6-4mff

## What is CVE-2020-6836?

CVE-2020-6836 is a critical code injection vulnerability in n/a, published on 11 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

grammar-parser.jison in the hot-formula-parser package before 3.0.1 for Node.js is vulnerable to arbitrary code injection. The package fails to sanitize values passed to the parse function and concatenates them in an eval call. If a value of the formula is taken from user-controlled input, it may allow attackers to run arbitrary commands on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

2 open source packages ship an affected version, including hot-formula-parser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hot-formula-parser` | npm | All versions | 3.0.1 |
| `hot-formula-parser` | npm | All versions | 3.0.1 |

Products: Hot-Formula-Parser Project Hot-Formula-Parser.

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

Upgrade hot-formula-parser to 3.0.1 or later.

## Is CVE-2020-6836 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6836 is a critical code injection vulnerability in n/a, published on 11 Jan 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-6836 in the wild and no public exploit code.

Affected packages and fixed versions:
- hot-formula-parser (npm): affected all versions; fixed in 3.0.1
- hot-formula-parser (npm): affected all versions; fixed in 3.0.1

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

## Sources

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

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