Quick answers
- Is CVE-2013-7454 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2013-7454 being exploited in the wild.
- How severe is CVE-2013-7454?
- Medium severity, with a CVSS score of 6.1, published 23 January 2017.
- Which products and versions are affected?
- validator (npm) SEMVER:introduced=0,fixed=1.1.0; Validator.Js Project Validator < 1.1.0.
- Is there a fix for CVE-2013-7454?
- Yes. validator (npm): upgrade to 1.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2013-7454 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2013-7454?
- Check whether you run Nodejs Node.Js, validator (npm) or Validator.Js Project Validator at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- validator (npm): upgrade to 1.1.0 or later
npm install validator@1.1.0
Technical details
The validator library for Node.js (versions prior to 1.1.0) is vulnerable to a Cross-Site Scripting (XSS) filter bypass. The vulnerability exists because the sanitization logic fails to recursively or effectively handle nested forbidden strings. A remote attacker can exploit this by submitting input containing nested tags or forbidden keywords that, when processed once, leave behind executable malicious code. This is a network-based attack that typically requires user interaction (UI:R) to execute the resulting script in the victim's browser context. The issue was addressed in version 1.1.0.
Affected products
- Node.js validator < 1.1.0
Identifiers
- CVE-2013-7454
- GHSA-q4qq-fm7q-cwp5
Timeline
- 2013-12-12: disclosed: Vulnerability identified (based on CVE year)
- 2017-01-23: advisory: NVD published the CVE details