# CVE-2018-6191: Integer overflow in n/a

> An integer overflow in the MuJS JavaScript engine allows attackers to cause denial of service or potentially execute arbitrary code.

- **Severity:** Medium 5.5 (`CVSS:3.0/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:** No
- **Published:** 24 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rrxp-jc5m-rx5p

## What is CVE-2018-6191?

CVE-2018-6191 is a medium-severity vulnerability in n/a, published on 24 Jan 2018. 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

The js_strtod function in jsdtoa.c in Artifex MuJS through 1.0.2 has an integer overflow because of incorrect exponent validation.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2018-6191?

It affects 1 product.


Products: Artifex Mujs.

## How do I fix CVE-2018-6191?

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

## Is CVE-2018-6191 being exploited?

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

Public exploit code:

- Artifex MuJS 1.0.2 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-33796](https://insights.sbomify.com/CVE-2021-33796/): Use after free in MuJS (critical 10.0)
- [CVE-2021-33797](https://insights.sbomify.com/CVE-2021-33797/): Integer overflow in mujs (critical 9.8)
- [CVE-2021-45005](https://insights.sbomify.com/CVE-2021-45005/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-12798](https://insights.sbomify.com/CVE-2019-12798/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-11411](https://insights.sbomify.com/CVE-2019-11411/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6191 and fix it if it is affected.

What it is: CVE-2018-6191 is a medium-severity vulnerability in n/a, published on 24 Jan 2018. 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: There is no known exploitation of CVE-2018-6191 in the wild and no public exploit code.

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

## Sources

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

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