CVE-2016-10141
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 · uneditedAn integer overflow vulnerability was observed in the regemit function in regexp.c in Artifex Software, Inc. MuJS before fa3d30fd18c348bb4b1f3858fb860f4fcd4b2045. The attack requires a regular expression with nested repetition. A successful exploitation of this issue can lead to code execution or a denial of service (buffer overflow) condition.
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 confidenceInteger overflow in MuJS regemit function in regexp.c allows specially crafted regex with nested repetition to trigger buffer overflow, potentially enabling code execution. The overflow occurs when calculating buffer sizes for regex emission.
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< 2017-01-12CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MuJS installation and versionLocate the MuJS library or executable in your environment and retrieve its version information using the method appropriate to your system (e.g., package manager query, library file metadata, or version flag if available from command-line interface)Affected if The installed version is any release of MuJS dated before 2017-01-12
-
Confirm regex functionality is in useAudit your application code or environment to determine whether the MuJS JavaScript engine is being used to process regular expressions, particularly any user-supplied or externally-sourced regex patternsAffected if The vulnerable regemit function in regexp.c is invoked when your code compiles or executes regular expressions through MuJS
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped2017-01-12
Upgrade MuJS to version after commit fa3d30fd or apply the fix to regemit function; implement regex input length/complexity limits as compensating control if upgrade is not feasible.
MuJS version built from commit fa3d30fd18c348bb4b1f3858fb860f4fcd4b2045 or later (dated 2017-01-12 or after)
- Identify all systems, applications, and dependencies using MuJS version earlier than 2017-01-12
- Locate the specific version of MuJS in use (check package.json, package-lock.json, or dependency management files)
- Obtain the fixed version of MuJS. The fix was committed as fa3d30fd18c348bb4b1f3858fb860f4fcd4b2045 on 2017-01-12. Use a version built at or after this date, or rebuild from source at the fixed commit
- Replace the vulnerable MuJS library with the fixed version in all affected deployments
- Restart any services or applications that link to the MuJS library to ensure the new version is loaded
- Test the updated application to verify functionality remains intact, particularly any code using regular expressions with nested repetition patterns
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10141 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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