CVE-2020-3299 json
Multiple Cisco Products SNORT HTTP Detection Engine File Policy Bypass Vulnerability
published 6y ago modified 2mo ago also EUVD-2020-24570
- cvss
- 5.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Multiple Cisco products are affected by a vulnerability in the Snort detection engine that could allow an unauthenticated, remote attacker to bypass a configured File Policy for HTTP. The vulnerability is due to incorrect detection of modified HTTP packets used in chunked responses. An attacker could exploit this vulnerability by sending crafted HTTP packets through an affected device. A successful exploit could allow the attacker to bypass a configured File Policy for HTTP packets and deliver a malicious payload.
Patch / fix
- cisco secure_firewall_threat_defense 6.3.0.1
- snort snort 2.9.13.1
Is CVE-2020-3299 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
2.31% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N |
| NVD | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- Cisco Cisco Firepower Threat Defense Software
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-ftd-bypass-3eCfd24j
vendor-advisory
-
debian.org
/security/2023/dsa-5354
vendor-advisory
-
lists.debian.org
/debian-lts-announce/2023/02/msg00011.html
mailing-list
Sources
- CVE List CVE-2020-3299
- NVD CVE-2020-3299
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.