LiveActive security incident?Get immediate response
CVE Record

CVE-2020-3299: Multiple Cisco Products SNORT HTTP Detection Engine File Policy Bypass Vulnerability

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.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let malicious files slip through HTTP file controls on affected Cisco/Snort-based inspection systems. It does not directly compromise the firewall, but it weakens a security control that may be relied on to block malware delivery.

Executive priority

Treat as a security-control bypass with moderate business urgency. Prioritize environments where Cisco/Snort inspection is a primary malware prevention layer for outbound or inbound HTTP traffic.

Technical view

The Snort HTTP detection engine mishandles modified packets in chunked HTTP responses. A remote unauthenticated attacker could send crafted HTTP traffic through an affected device and bypass a configured HTTP File Policy, enabling delivery of content that should have been blocked.

Likely exposure

Relevant exposure includes Cisco Firepower Threat Defense and other Cisco products using the affected Snort engine, plus Debian Snort packages referenced by Debian advisories. Risk depends on inline HTTP inspection and File Policy use. Exact affected versions are not provided in the prompt bundle.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The attack is network-reachable, unauthenticated, and low-complexity, but impact is limited to bypassing an HTTP file policy rather than direct system takeover.

Researcher notes

Evidence supports a CWE-693 protection-mechanism failure in Snort HTTP chunked-response handling. The bundle does not provide fixed Cisco version ranges, affected non-FTD Cisco product names, proof-of-concept status, or exploitation telemetry.

Mitigation direction

  • Review Cisco advisory guidance for affected products and fixed releases.
  • Apply Cisco software or rule-engine updates where applicable.
  • Apply Debian Snort security updates on Debian-managed systems.
  • Do not rely only on HTTP File Policy for malware blocking.
  • Use layered controls for web, endpoint, and email content inspection.

Validation and detection

  • Inventory Cisco FTD and Snort deployments handling HTTP traffic.
  • Confirm whether HTTP File Policy is configured and enforced inline.
  • Compare installed versions against Cisco and Debian advisories.
  • Verify security update deployment through package or appliance management records.
  • Review monitoring for unexpected malicious file delivery over HTTP.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-693: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-3299 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.8CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.8Medium
CVSS 3.0 vector shape for CVE-2020-3299Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CiscoCisco Firepower Threat Defense Softwaren/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.