DNS Rebinding Vulnerability in mitmproxy: CVE-2018-14505

mitmproxy Updated 02 Oct 2025

Summary

22/07/2018
N/A
Yes i
High
8.8

CVE-2018-14505: mitmweb in mitmproxy v4.0.3 allows DNS Rebinding attacks, related to tools/web/app.py. Affects mitmproxy across 2 version ranges.

< 3.0.4-1 < b62b119779dac8fa6b992fa225c46b7b7e9e0f88

Fixed in 3.0.4-1. How to fix ↓

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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

mitmproxy is an open-source proxy tool that allows developers to intercept, inspect, modify, and replay web traffic. It is widely used for debugging and testing web applications. The tool provides a user-friendly interface and supports various protocols, making it a popular choice among developers. However, in version 4.0.3, mitmproxy is vulnerable to DNS Rebinding attacks, which can compromise the security of applications relying on it.

Vulnerability Detail

CVE-2018-14505 is a vulnerability in mitmproxy that allows attackers to exploit DNS Rebinding techniques. This vulnerability arises from improper handling of DNS responses, enabling an attacker to redirect traffic to malicious servers. The ramifications include unauthorized access to sensitive data, potential data manipulation, and the ability to perform actions on behalf of the user without their consent. The vulnerability affects versions prior to 3.0.4-1, and it is crucial for users to understand the risks associated with using affected versions.

How To Fix

Minimum fixed version

3.0.4-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade mitmproxy

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading is not immediately possible, consider implementing network-level protections such as firewalls that can block malicious DNS requests. Additionally, avoid using mitmproxy in environments where sensitive data is transmitted until the vulnerability is resolved.

Conclusion

CVE-2018-14505 represents a significant security risk for users of mitmproxy version 4.0.3 and earlier. It is essential to upgrade to the latest version to protect against DNS Rebinding attacks. Users should also consider using tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for mitmproxy →

Share this vulnerability

FAQ

DNS Rebinding is a technique that allows an attacker to manipulate the DNS resolution process, redirecting a victim's browser to a malicious server while appearing to be a legitimate site.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Simply upload your manifest file like package-lock.json to check for vulnerabilities.

The potential impacts include unauthorized access to sensitive information, data manipulation, and the ability for attackers to perform actions on behalf of the user.

Yes, implementing network-level protections and avoiding the use of mitmproxy in sensitive environments can help mitigate the risk until an upgrade is possible.

The CVSS score for CVE-2018-14505 is 8.8, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for mitmproxy.

How To Fix

Minimum fixed version

3.0.4-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade mitmproxy

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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