dbcve.org
MujsApplication · Artifex

CVE-2017-5627

HIGH · 7.8 CVSS v3.1 Published 2017-01-30
Fix available
A fix is available. Upgrade to 2017-01-24 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MuJS JavaScript engine fails to validate array length in jsR_setproperty, allowing negative values that cause integer overflow in js_pushstring. This memory corruption vulnerability can be triggered by parsing maliciously crafted JS files, potentially enabling arbitrary code execution.

MitigationUpdate MuJS to version after commit 4006739a28367c708dea19aeb19b8a1a9326ce08. Until then, avoid processing untrusted JavaScript files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MujsApplication
Affected:< 2017-01-24

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate MuJS installation
    Search for mujs binary or library files on the system using 'which mujs', 'find /usr -name "*mujs*"', or check common installation paths like /usr/bin/mujs, /usr/local/bin/mujs, or library directories.
    Affected if MuJS is not found on the system (not applicable).
  2. Determine installed MuJS version
    Run 'mujs --version' or check the library version if using libmujs (e.g., 'dpkg -l libmujs0' on Debian-based systems, 'rpm -qa | grep mujs' on RHEL-based systems).
    Affected if The version displayed is dated before 2017-01-24, or the version string cannot be determined.
  3. Verify if application processes untrusted JavaScript
    Inspect application configuration, source code, or runtime settings to determine if the MuJS engine is used to parse JavaScript files from untrusted sources (user uploads, network inputs, or external APIs).
    Affected if The application processes JavaScript from untrusted sources while using a vulnerable MuJS version.

A system is affected if it runs MuJS version dated before 2017-01-24 AND processes untrusted JavaScript files through that engine.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2017-01-24 or later
Fixed in 2017-01-24
Interim mitigation

Update MuJS to version after commit 4006739a28367c708dea19aeb19b8a1a9326ce08. Until then, avoid processing untrusted JavaScript files.

Fix this in Mujs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5627 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data