Quick answers
- Is CVE-2024-37169 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-37169 being exploited in the wild.
- How severe is CVE-2024-37169?
- Low severity, with a CVSS score of 3.1, published 5 June 2024.
- Which products and versions are affected?
- @jmondi/url-to-png (npm) SEMVER:introduced=0,fixed=2.0.3.
- Is there a fix for CVE-2024-37169?
- Yes. @jmondi/url-to-png (npm): upgrade to 2.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-37169 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-37169?
- Check whether you run @jmondi/url-to-png (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
- @jmondi/url-to-png (npm): upgrade to 2.0.3 or later
npm install @jmondi/url-to-png@2.0.3
Technical details
The vulnerability is a path traversal / arbitrary file read flaw (CWE-22) in the screenshot feature that accepts file:// protocol URLs. The vulnerable component fails to validate or restrict the URL protocol before passing it to Playwright's screenshot function, allowing an attacker to read any file accessible to the application process. No authentication or user interaction is required; exploitation is triggered by supplying a malicious URL to the application. The attack is network-reachable and exploitable with no privileges required. A fix was released in v2.0.3, which restricts accepted URLs to http and https protocols only.
Affected products
- jasonraimondi @jmondi/url-to-png < 2.0.3
Identifiers
- CVE-2024-37169
- GHSA-665w-mwrr-77q3
Timeline
- 2024-06-05: disclosed: Security advisory published
- 2024-06-05: patched: Version 2.0.3 released with fix restricting URLs to http/https protocols