CVE-2019-1669
Summary
| CVE | CVE-2019-1669 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2019-01-24 16:29:00 UTC |
| Updated | 2019-10-09 23:47:00 UTC |
| Description | A vulnerability in the data acquisition (DAQ) component of Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to bypass configured access control policies or cause a denial of service (DoS) condition. The vulnerability exists because the affected software improperly manages system memory resources when inspecting traffic. An attacker could exploit this vulnerability by generating specific traffic patterns for the software to inspect. A successful exploit could allow the attacker to exhaust system memory resources used for traffic inspection. Depending on the configuration, the FTD Software could fail open and cease to inspect traffic or fail closed and result in a DoS condition. This vulnerability may require manual intervention to restore the software. |
Risk And Classification
Problem Types: CWE-693
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Cisco | Firepower Threat Defense | 6.3.0 | All | All | All |
| Application | Cisco | Firepower Threat Defense | 6.4.0 | All | All | All |
| Application | Cisco | Firepower Threat Defense | 6.3.0 | All | All | All |
| Application | Cisco | Firepower Threat Defense | 6.4.0 | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Cisco Firepower Threat Defense Software Packet Inspection and Enforcement Bypass Vulnerability | CISCO | tools.cisco.com | Vendor Advisory |
| Cisco Firepower Threat Defense CVE-2019-1669 Security Bypass Vulnerability | BID | www.securityfocus.com | Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.