Quick answers
- Is CVE-2013-7452 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2013-7452 being exploited in the wild.
- How severe is CVE-2013-7452?
- 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-7452?
- 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-7452 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2013-7452?
- 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
A vulnerability exists in the validator library for Node.js (versions prior to 1.1.0) where the XSS filtering logic fails to properly sanitize 'javascript:' URIs. By crafting a specific URI, a remote attacker can bypass the filter to inject and execute arbitrary JavaScript in the context of the victim's browser session. This is a classic XSS filter bypass that occurs during input validation or sanitization. The issue is resolved in version 1.1.0 and later. Exploitation typically requires a user to interact with a malicious link or for the application to render the unsanitized input.
Affected products
- Node.js validator < 1.1.0
Identifiers
- CVE-2013-7452
- GHSA-rh6c-q938-3r9q
Timeline
- 2013-12-12: disclosed: Original vulnerability discovery date (based on CVE year)
- 2016-04-20: advisory: Public disclosure on oss-security mailing list
- 2017-01-23: advisory: NVD publication date