SafeURL-Python's hostname blocklist does not block FQDNs
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Description If a hostname was blacklisted, it was possible to bypass the blacklist by requesting the FQDN of the host (e.g. adding `.` to the end). ### Impact The main purpose of this library is to block requests to internal/private IPs and these cannot be bypassed using this finding. But if a library user had specifically set certain hostnames as blocked, then an attacker would be able to circumvent that block to cause SSRFs to request those hostnames. ### Patches Fixed by https://github.com/IncludeSecurity/safeurl-python/pull/6 ### Credit https://github.com/Sim4n6
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | SafeURL-Python (PyPI) | before 1.3 | 1.3 | Patch available | GHSA-373w-rj84-pv6x |
- SafeURL-Python (PyPI) Vendor— Affected before 1.3 Fixed in 1.3 Patch available GHSA-373w-rj84-pv6x
Remediation
- Fix · GHSA-373w-rj84-pv6x SafeURL-Python (PyPI) Fixed in 1.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-373w-rj84-pv6x
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences