Forced Browsing in Twisted
Twisted before 16.3.1 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the `HTTP_PROXY` environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an `httpoxy` issue.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-1000111US | medium5.3 | — | ||
Twisted before 16.3.1 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2016-3090545.htmlWEB
- https://github.com/pypa/advisory-database/tree/main/vulns/twisted/PYSEC-2020-214.yamlWEB
- https://github.com/twisted/twistedPACKAGE
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000111ADVISORY
- https://twistedmatrix.com/pipermail/twisted-web/2016-August/005268.htmlWEB
- https://twistedmatrix.com/trac/ticket/8623WEB
- https://www.openwall.com/lists/oss-security/2016/07/18/6WEB
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