Quick answers
- Is CVE-2022-0613 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-0613 being exploited in the wild.
- How severe is CVE-2022-0613?
- Low severity, with a CVSS score of 3.1, published 17 February 2022.
- Which products and versions are affected?
- urijs (npm) SEMVER:introduced=0,fixed=1.19.8.
- Is there a fix for CVE-2022-0613?
- Yes. urijs (npm): upgrade to 1.19.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-0613 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-0613?
- Check whether you run urijs (npm) 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
- urijs (npm): upgrade to 1.19.8 or later
npm install urijs@1.19.8
Technical details
The vulnerability is an authorization bypass in urijs due to case-insensitive scheme handling (CWE-639). The library's scheme validation logic was case-sensitive, allowing attackers to bypass security controls implemented in patch CVE-2021-3647 by using mixed-case protocol schemes (e.g., HTTP, htTP) in URIs. No authentication is required; this is a network-reachable vulnerability affecting any application that relies on urijs for URI validation and authorization decisions. An attacker can bypass URL-based access controls, potentially leading to unauthorized access to protected resources. The vulnerability was fixed in version 1.19.8 with a commit implementing case-insensitive scheme parsing.
Affected products
- urijs before 1.19.8
Identifiers
- CVE-2022-0613
- GHSA-gcv8-gh4r-25x6
Timeline
- 2022-02-17: disclosed
- 2022-02-17: patched: Fixed in version 1.19.8