Aggregates CVE and security vulnerability intelligence across all bottlepy-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Historical issues mainly involve vendor risk input validation and related problems; some flaws may lead to vendor impact unexpected behavior, affecting vendor surface software deployment scenarios.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2022-31799 | Bottle before 0.12.20 mishandles errors during early request binding. | [email protected] | 9.8 | 1.87% | 2022-06-02 | 2024-11-21 |
| CVE-2020-28473 | The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not | [email protected] | 6.8 | 1.84% | 2021-01-18 | 2024-11-21 |
| CVE-2016-9964 | redirect() in bottle.py in bottle 0.12.10 doesn't filter a "\r\n" sequence, which leads to a CRLF attack, as demonstrated by a redirect("233\r\nSet-Cookie: name=salt") call. | [email protected] | 6.5 | 1.76% | 2016-12-16 | 2026-05-06 |
| CVE-2014-3137 | Bottle 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 does not properly limit content types, which allows remote attackers to bypass intended access restrictions via an accepted Content-Type followed by a ; (semi-colon) and a Content-Type that would not be accepted, as demonstrated in YouCompleteMe to execute arbitrary code. | [email protected] | 6.8 | 3.10% | 2014-10-25 | 2026-05-06 |