dbcve.org
Riot CompilerApplication · Riot.js

CVE-2016-10527

HIGH · 7.5 CVSS v3.0 Published 2018-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The riot-compiler version version 2.3.21 has an issue in a regex (Catastrophic Backtracking) thats make it unusable under certain conditions.

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 · moderate confidence

The riot-compiler version 2.3.21 contains a Regular Expression Denial of Service (ReDoS) vulnerability caused by catastrophic backtracking. When the vulnerable regex processes certain input patterns, it can cause exponential time complexity, making the compiler hang or become extremely slow.

MitigationUpdate the vulnerable regex pattern to use atomic groups, possessive quantifiers, or a simplified pattern to prevent backtracking. Alternatively, upgrade to a patched version of riot-compiler if available.

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
Riot CompilerApplication
Affected:= 2.3.21

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 riot-compiler in your project
    Check your project's package.json file for 'riot-compiler' in the dependencies or devDependencies section, or inspect node_modules/riot-compiler/package.json if node_modules exists.
    Affected if The package is listed in dependencies or installed in node_modules.
  2. Identify the installed version
    Run 'npm list riot-compiler' in your project directory, or open node_modules/riot-compiler/package.json and read the 'version' field.
    Affected if You are able to retrieve a version number from the package.
  3. Compare against the vulnerable version
    Verify whether the installed version is exactly 2.3.21.
    Affected if The installed version equals 2.3.21 exactly.
  4. Confirm the package is actively used
    Search your project source for imports or requires of 'riot-compiler', or check build scripts that invoke the compiler.
    Affected if Your build process or code imports and executes riot-compiler.

You are affected if riot-compiler version 2.3.21 is installed and used in your environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the vulnerable regex pattern to use atomic groups, possessive quantifiers, or a simplified pattern to prevent backtracking. Alternatively, upgrade to a patched version of riot-compiler if available.

Fix this in Riot Compiler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10527 — 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-2016-10527 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