CVE-2016-10520: Regular Expression Denial of Service in jadedown

jadedown Updated 02 Oct 2025

Summary

18/02/2019
No i
Low
Not published

CVE-2016-10520: Regular Expression Denial of Service in jadedown. Affects jadedown versions < 0.0.3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The jadedown package is an npm package that provides a templating language for processing user input. It has not been actively maintained since 2011. The package is vulnerable to a regular expression denial of service (ReDoS) attack when certain types of user input are passed in.

Vulnerability Detail

The vulnerability in the jadedown package allows an attacker to cause a denial of service (DoS) by sending specially crafted input. This is due to the way the package handles regular expressions, which can be exploited to cause the application to hang or crash. The impact of this vulnerability can range from a temporary disruption of service to a complete system failure.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If the jadedown package is used to process user input and cannot be immediately replaced, a possible workaround is to implement input validation and sanitization to prevent malicious input from triggering the vulnerability. This can be done by using libraries or custom code to validate and sanitize user input before passing it to the jadedown package.

Conclusion

The jadedown package is vulnerable to a regular expression denial of service (ReDoS) attack. Since the package is no longer actively maintained, the best solution is to refactor the dependent application to not use this module. Implementing input validation and sanitization can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for jadedown →

Share this vulnerability

FAQ

The impact of this vulnerability can range from a temporary disruption of service to a complete system failure, depending on the severity of the attack and the resources available to the attacker.

No, there is no patch available for this vulnerability as the jadedown package is no longer actively maintained. The recommended solution is to refactor the dependent application to not use this module.

Yes, a possible workaround is to implement input validation and sanitization to prevent malicious input from triggering the vulnerability. This can be done by using libraries or custom code to validate and sanitize user input before passing it to the jadedown package.

Yes, this vulnerability can be exploited remotely by sending specially crafted input to the application that uses the jadedown package.

There is no known public exploit for this vulnerability at the moment. However, the vulnerability is well-documented and can be easily exploited by an attacker with knowledge of the issue.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback