CVE-2020-35471: Envoy before 1.16.1 mishandles dropped and truncated datagrams, as demonstrated by a segmentation fault for a UDP packet size larger than…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 84.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: envoy-proxy (openSUSE:Leap 15.3) 1.14.6-bp153.3.4.1; envoy-proxy (SUSE:Package Hub 15 SP3) 1.14.6-bp153.3.4.1.
Low priority for now. Upgrade to envoy-proxy (openSUSE:Leap 15.3) 1.14.6-bp153.3.4.1; envoy-proxy (SUSE:Package Hub 15 SP3) 1.14.6-bp153.3.4.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Envoy before 1.16.1 mishandles dropped and truncated datagrams, as demonstrated by a segmentation fault for a UDP packet size larger than 1500.
- Published
- Dec 14, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.3% · 84th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| envoyproxy | envoy | cpe:2.3:a:envoyproxy:envoy |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- envoyproxy envoybefore 1.16.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.3 | envoy-proxy | before 1.14.6-bp153.3.4.1 | 1.14.6-bp153.3.4.1 |
| SUSE:Package Hub 15 SP3 | envoy-proxy | before 1.14.6-bp153.3.4.1 | 1.14.6-bp153.3.4.1 |
Same product
envoyproxy: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-30255HTTP/2: CPU exhaustion due to CONTINUATION frame flood56Plan
- CVE-2024-27919HTTP/2: memory exhaustion due to CONTINUATION frame flood55Plan
- CVE-2021-29492Bypass of path matching rules using escaped slash characters52Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-25018Oct 1, 2020 · Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization.30Monitor
- ← EarlierCVE-2020-35470Dec 14, 2020 · Envoy before 1.16.1 logs an incorrect downstream address because it considers only the directly connected peer, not the information in the…35Monitor
- Later →CVE-2021-21378Mar 10, 2021 · JWT authentication bypass with unknown issuer token33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:envoy-proxy | 1.14.6-bp153.3.4.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:envoy-proxy | 1.14.6-bp153.3.4.1 · SUSE:Package Hub 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.