Skip to content
Fencer Intel
low —

GHSA-373w-rj84-pv6x json

SafeURL-Python's hostname blocklist does not block FQDNs

published 3y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

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

Patch / fix

  • pypi safeurl-python 1.3

Is GHSA-373w-rj84-pv6x in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi safeurl-python
<1.3
1.3

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.