CVE-2014-3137: Bottle Content-Type Limitation Bypass

bottle Updated 02 Oct 2025

Summary

17/05/2022
Yes i
High
9.8

CVE-2014-3137: Bottle does not properly limit content-types. Affects bottle across 3 version ranges.

>= 0.10.0, < 0.10.12 >= 0.11.0, < 0.11.7 >= 0.12.0, < 0.12.6

Fixed in 0.10.12, 0.11.7 or 0.12.6, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2014-3137 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Bottle is a lightweight and fast Python web framework that allows developers to build web applications. It is known for its simplicity and ease of use. However, versions 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 of Bottle have a vulnerability that allows remote attackers to bypass access restrictions. This vulnerability arises from the improper limitation of content types in the framework.

Vulnerability Detail

The vulnerability in Bottle arises from the improper limitation of content types. Attackers can exploit this vulnerability by sending a request with an accepted Content-Type followed by a ; (semi-colon) and a Content-Type that would not be accepted. This allows them to bypass intended access restrictions. An attacker can leverage this vulnerability to execute arbitrary code. The vulnerability has been demonstrated in YouCompleteMe.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 0.10.0, < 0.10.12 0.10.12
    pip install --upgrade "bottle==0.10.12"
  • >= 0.11.0, < 0.11.7 0.11.7
    pip install --upgrade "bottle==0.11.7"
  • >= 0.12.0, < 0.12.6 0.12.6
    pip install --upgrade "bottle==0.12.6"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of Bottle to mitigate the risk.

Conclusion

The vulnerability in Bottle allows remote attackers to bypass access restrictions and execute arbitrary code. It is crucial to upgrade to the fixed version of Bottle to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for bottle →

Share this vulnerability

FAQ

Bottle is a lightweight and fast Python web framework used for building web applications.

Versions 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 of Bottle are affected.

An attacker can exploit this vulnerability by sending a request with an accepted Content-Type followed by a ; (semi-colon) and a Content-Type that would not be accepted, bypassing access restrictions and executing arbitrary code.

No, there is no known workaround for this vulnerability. Upgrading to the fixed version of Bottle is necessary.

To fix this vulnerability, upgrade to version 0.10.12 or later for 0.10.x, version 0.11.7 or later for 0.11.x, and version 0.12.6 or later for 0.12.x of Bottle.

Related vulnerabilities

Recent vulnerabilities recorded for bottle.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 0.10.0, < 0.10.12 0.10.12
    pip install --upgrade "bottle==0.10.12"
  • >= 0.11.0, < 0.11.7 0.11.7
    pip install --upgrade "bottle==0.11.7"
  • >= 0.12.0, < 0.12.6 0.12.6
    pip install --upgrade "bottle==0.12.6"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback