# CVE-2016-9017: Information disclosure in n/a

> Attackers can obtain sensitive information via out-of-bounds read in MuJS by crafting a malicious JavaScript file.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-527p-fff3-w4mq

## What is CVE-2016-9017?

CVE-2016-9017 is a high-severity vulnerability in n/a, published on 28 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Artifex Software, Inc. MuJS before a5c747f1d40e8d6659a37a8d25f13fb5acf8e767 allows context-dependent attackers to obtain sensitive information by using the "opname in crafted JavaScript file" approach, related to an "Out-of-Bounds read" issue affecting the jsC_dumpfunction function in the jsdump.c component.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2016-9017?

It affects 1 product.


Products: Artifex Mujs.

## How do I fix CVE-2016-9017?

Apply the vendor's patch.

## Is CVE-2016-9017 being exploited?

There is no known exploitation of CVE-2016-9017 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-2016-9017 and fix it if it is affected.

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

## Sources

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

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