Quick answers
- Is CVE-2022-25876 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-25876 being exploited in the wild.
- How severe is CVE-2022-25876?
- Low severity, with a CVSS score of 3.1, published 2 July 2022.
- Which products and versions are affected?
- link-preview-js (npm) SEMVER:introduced=0,fixed=2.1.17.
- Is there a fix for CVE-2022-25876?
- Yes. link-preview-js (npm): upgrade to 2.1.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-25876 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-25876?
- Check whether you run link-preview-js (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
- link-preview-js (npm): upgrade to 2.1.17 or later
npm install link-preview-js@2.1.17
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) flaw caused by flawed DNS rebinding protection in link-preview-js versions before 2.1.17. An attacker can craft malicious input to bypass the DNS rebinding defenses, allowing them to make arbitrary HTTP requests to internal network addresses and read responses. This affects any application that uses the library to fetch link previews from user-supplied URLs without proper network isolation. The vulnerability was patched in version 2.1.17.
Affected products
- ospfranco link-preview-js before 2.1.17
Identifiers
- CVE-2022-25876
- GHSA-h9cw-7g8j-h66h
Timeline
- 2022-07-02: disclosed
- 2022-07-02: patched: Fixed in version 2.1.17