Ettercap through 0.8.4.1 Out-of-Bounds Read via sslw_remove_sts
Affects Ettercap through 0.8.4.1 when SSL MITM or sslstrip interception is active. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Ettercap through 0.8.4.1 contains an out-of-bounds read and size_t underflow vulnerability in sslw_remove_sts() in src/ec_sslwrap.c, caused by a stale length and an unchecked memmem() result when stripping Strict-Transport-Security headers. A malicious HTTPS server whose response passes through Ettercap's SSL interception can trigger out-of-bounds reads and memory corruption in the Ettercap process, which normally runs as root.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Ettercap ettercap
through 0.8.4.1
Evidence 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125403
Is CVE-2026-125403 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A server response carrying a Strict-Transport-Security header with no CRLF after it makes Ettercap read past the end of a buffer. This can crash the process and corrupt heap memory, using a memcpy length the attacker controls, in a process that normally runs as root.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-125403?
ettercap: through 0.8.4.1.Source: cve.now feed data
Am I affected, and how do I check?
The product range in scope is Ettercap through 0.8.4.1. The bug needs SSL MITM or sslstrip interception to be active, with the victim client reaching an attacker-controlled or attacker-influenced HTTPS server. To check a setup, confirm the installed Ettercap version and whether SSL MITM or sslstrip is enabled.Source: vulncheck.com, github.com
How do I fix CVE-2026-125403?
The checked facts list no fixed version, so no upgrade target is available from them. Check the Ettercap project or vendor for a release later than 0.8.4.1 before deciding on an upgrade.Source: vulncheck.com, github.com