Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Bottle before 0.12.20 mishandles errors during early request binding.
Recommended action: Upgrade to 0.12.20 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 0.12.6, 0.11.7 or 0.10.12 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
bottle.py is a fast and simple micro-framework for python web-applications. 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.
Recommended action: Upgrade to 0.12.11 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The package bottle 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 include it in a cache key of an unkeyed parameter.
Recommended action: Upgrade to 0.12.19 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.