Approved changes feed: RSS · Atom
cpe:2.3:a:felippe-regazio:ssrfcheck:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Felippe Regazio (b16c7796-6f9c-5524-89d1-cc97b0015060) |
|---|---|
| Product | Ssrfcheck (4b069ad5-7e33-5bd6-894f-3912daace391) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-43929 |
vulnerable | 2026-06-08 08:03:18.022150 |
ssrfcheck: Server-Side Request Forgery (SSRF) and Incomplete List of Disallowed Inputs
HIGH (8.2)
ssrfcheck is a library that checks if a string contains a potential SSRF attack. In 1.3.0 and earlier, ssrfcheck fails to block Server-Side Request Forgery attacks when the target private IP address is encoded as an IPv4-mapped IPv6 address (e.g. http://[::ffff:127.0.0.1]/). The WHATWG URL parser built into Node.js silently normalizes the IPv4 notation inside the brackets to compressed hex form ([::ffff:7f00:1]) before the library's private-IP regex ever runs. The regex was written to match dot-notation only and therefore never matches any real input — all seven IANA private IPv4 ranges, including the AWS/GCP/Azure metadata address 169.254.169.254, are bypassed. Any application using isSSRFSafeURL() to guard HTTP requests made with user-supplied URLs is fully exposed to SSRF.
Published: 2026-05-12T17:49:12.192Z
Updated: 2026-05-13T14:37:49.368Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.