Quick answers
- Is CVE-2019-5448 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-5448 being exploited in the wild.
- How severe is CVE-2019-5448?
- Low severity, with a CVSS score of 3, published 31 July 2019.
- Which products and versions are affected?
- yarn (npm) SEMVER:introduced=0,fixed=1.17.3.
- Is there a fix for CVE-2019-5448?
- Yes. yarn (npm): upgrade to 1.17.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2019-5448 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2019-5448?
- Check whether you run yarn (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
- yarn (npm): upgrade to 1.17.3 or later
npm install yarn@1.17.3
Technical details
This vulnerability stems from Yarn's use of HTTP (unencrypted) URLs in lockfiles, which causes authentication tokens and credentials to be sent in plaintext over the network. The vulnerability affects all versions before 1.17.3. An attacker positioned to intercept network traffic (e.g., on a shared network or via a compromised router) can capture these unencrypted authentication credentials. The fix involves using HTTPS URLs or other secure mechanisms to prevent credential exposure. The issue was publicly disclosed and patched in Yarn 1.17.3.
Affected products
- Yarn Yarn before 1.17.3
Identifiers
- CVE-2019-5448
- GHSA-wqfc-cr59-h64p
Timeline
- 2019-07-31: disclosed
- 2019-07-12: patched: Security update released