safeurl-python
Affected
- introduced
0, fixed1.2(ecosystem)
Fixed versions
1.2
Fix
- Fixed version
1.2pip install --upgrade safeurl-python==1.2
Advisory
Also known as: CVE-2023-24622, PYSEC-2023-298
safeurl-python contains Server-Side Request Forgery
Description
In SafeURL it is possible to specify a list of domains that should be matched before a request is sent out. The regex used to compare domains did not work as intended.
Impact
The regex used was:
re.match("(?i)^%s" % domain, value)
This has two problems, first that only the beginning and not the end of the string is anchored. Second, that a dot in the domain matches any character as part of regex syntax.
Therefore, an allowlist of ["victim.com"] could allow the domain "victimacomattacker.com" to be requested.
This has lower impact since the usual attacker aim in an SSRF is to request internal resources such as private IP addresses rather than an attacker's own domain. But, in a case where SafeURL had specifically been used to try to limit requests to a particular allowlist, say for example a PDF renderer, the finding would be more severe.
Patches
Fixed in https://github.com/IncludeSecurity/safeurl-python/pull/5
References
Server-side request forgery (SSRF)
Medium Basis: The source's own band: MODERATE
0, fixed 1.2 (ecosystem)1.2
1.2pip install --upgrade safeurl-python==1.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0