Server-side Request Forgery (SSRF) in hackney
Versions of the package hackney from 0.0.0 are vulnerable to Server-side Request Forgery (SSRF) due to improper parsing of URLs by URI built-in module and hackey. Given the URL http://127.0.0.1?@127.2.2.2/, the URI function will parse and see the host as 127.0.0.1 (which is correct), and hackney will refer the host as 127.2.2.2/. This vulnerability can be exploited when users rely on the URL function for host checking.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-1211US | — | — | ||
Versions of the package hackney before 1.21.0 are vulnerable to Server-side Request Forgery (SSRF) due to improper parsing of URLs by URI built-in module and hackey. Given the URL… | ||||
02
references
External citations — patches, advisories, analysis.
- https://gist.github.com/snoopysecurity/996de09ec0cfd0ebdcfdda8ff515deb1WEB
- https://github.com/benoitc/hackneyPACKAGE
- https://github.com/benoitc/hackney/commit/9594ce58fabd32cd897fc28fae937694515a3d4aWEB
- https://github.com/benoitc/hackney/releases/tag/1.21.0WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-1211ADVISORY
- https://security.snyk.io/vuln/SNYK-HEX-HACKNEY-6516131WEB
- https://www.blackhat.com/docs/us-17/thursday/us-17-Tsai-A-New-Era-Of-SSRF-Exploiting-URL-Parser-In-Trending-Programming-Languages.pdfWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan