# CVE-2017-5627: Integer overflow in n/a

> An integer overflow in MuJS allows attackers to execute arbitrary code or cause denial of service via a crafted JavaScript file.

- **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:** Yes
- **Published:** 30 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9949-26g4-c4fx

## What is CVE-2017-5627?

CVE-2017-5627 is a high-severity vulnerability in n/a, published on 30 Jan 2017. 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

An issue was discovered in Artifex Software, Inc. MuJS before 4006739a28367c708dea19aeb19b8a1a9326ce08. The jsR_setproperty function in jsrun.c lacks a check for a negative array length. This leads to an integer overflow in the js_pushstring function in jsrun.c when parsing a specially crafted JS file.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2017-5627?

It affects 1 product.


Products: Artifex Mujs.

## How do I fix CVE-2017-5627?

Apply the vendor's patch.

## Is CVE-2017-5627 being exploited?

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

## 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-2017-5627 and fix it if it is affected.

What it is: CVE-2017-5627 is a high-severity vulnerability in n/a, published on 30 Jan 2017. 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-2017-5627 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-2017-5627/ (Markdown: https://insights.sbomify.com/CVE-2017-5627/index.md)
```

## Sources

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

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