← Back to results
Vulnerability record · public intelligence
CVE-2017-20162
MEDIUM

Vercel ms Inefficient Regular Expression Complexity vulnerability

Published Jan 5, 2023 · Updated Oct 23, 2026 · Also known as GHSA-w9mr-4mfr-499f

Severity · CVSSMEDIUM · 4.3
Known exploitationNot listed
EPSS / likelihood1.02%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Vercel ms Inefficient Regular Expression Complexity vulnerability

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A vulnerability, which was classified as problematic, has been found in vercel ms up to 1.x. This issue affects the function parse of the file index.js. The manipulation of the argument str leads to inefficient regular expression complexity. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is caae2988ba2a37765d055c4eee63d383320ee662. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217451.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GHSA-w9mr-4mfr-499f

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. vuldb.com ↗
  2. vuldb.com ↗
  3. Source repository ↗
  4. Patch commit ↗
  5. Source repository ↗
  6. security.netapp.com ↗

Record history

Published Jan 5, 2023 · Last refreshed Oct 23, 2026