Skip to content
Fencer Intel
medium 5.3

CVE-2017-16137 json

Regular Expression Denial of Service in debug

published 2018-06-07 8 y ago modified 2026-10-15 25 d ago also GHSA-gxpj-cx7g-858c , EUVD-2018-0400

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

The debug module is vulnerable to regular expression denial of service when untrusted user input is passed into the o formatter. It takes around 50k characters to block for 2 seconds making this a low severity issue.

Patch / fix

  • npm debug 2.6.9, 3.1.0, 3.2.7, 4.3.1
  • debug_project debug 2.6.9, 3.1.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-16137 updated cvss 5.3

nodejs-debug: Regular expression Denial of Service

  • Red Hat OpenShift Enterprise 3 nodejs-debug Red Hat Software Collections rh-nodejs4-nodejs-debug, rh-nodejs6-nodejs-debug, rh-nodejs8-nodejs-debug
    affected: no fix planned “Will not fix”
  • Red Hat Virtualization 4 ovirt-engine-api-explorer
    affected: no fix planned “Out of support scope”
  • Red Hat Quay v3 quay/quay-rhel8 v3.6.0-62
    fixed: vendor fix RHSA-2021:3917
  • Red Hat Quay v3 quay/clair-rhel8 v3.6.0-70, quay/quay-builder-rhel8 v3.6.0-44, quay/quay-operator-rhel8 v3.6.0-43, quay/quay-operator-bundle v3.6.0-48, quay/quay-bridge-operator-rhel8 v3.6.0-40, quay/quay-bridge-operator-bundle v3.6.0-35, +3 more Red Hat Mobile Application Platform 4 rhmap-fh-aaa-docker, rhmap-fh-scm-docker, rhmap-fh-ngui-docker, rhmap-fh-mbaas-docker, rhmap-fh-statsd-docker, rhmap-fh-metrics-docker, +3 more Red Hat Virtualization 4 ovirt-engine-dashboard, ovirt-engine-ui-extensions
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
25 d ago

Exploit prediction

2.83% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm debug
<2.6.9
>=3.0.0, <3.1.0
>=3.2.0, <3.2.7
>=4.0.0, <4.3.1
2.6.9
3.1.0
3.2.7
4.3.1

Affected products

  • HackerOne debug node module

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.