dbcve.org
Firepower Services Software For AsaApplication · Cisco

CVE-2019-1982

MEDIUM · 5.3 CVSS v3.1 Published 2019-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the HTTP traffic filtering component of Cisco Firepower Threat Defense Software, Cisco FirePOWER Services Software for ASA, and Cisco Firepower Management Center Software could allow an unauthenticated, remote attacker to bypass filtering protections. The vulnerability is due to improper handling of HTTP requests, including those communicated over a secure HTTPS connection, that contain maliciously crafted headers. An attacker could exploit this vulnerability by sending malicious requests to an affected device. An exploit could allow the attacker to bypass filtering and deliver malicious requests to protected systems, allowing attackers to deliver malicious content that would otherwise be blocked.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in Cisco Firepower's HTTP traffic filtering allows unauthenticated remote attackers to bypass filtering protections by sending HTTP requests (including HTTPS) with maliciously crafted headers. The improper handling of these headers allows malicious content through that would otherwise be blocked.

MitigationApply Cisco vendor patches/updates for Firepower Threat Defense, FirePOWER Services for ASA, and Firepower Management Center to fix the improper HTTP header handling in the filtering component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Firepower Services Software For AsaApplication
Affected:all versions
Secure Firewall Management CenterApplication
Affected:= 2.9.13= 2.9.14.0= 3.0.0
Secure Firewall Threat DefenseApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Cisco Firepower product and version
    On the Firepower Management Center, go to System > Updates or use the command 'show version' on the device CLI to identify the exact product name (Firepower Services for ASA, Firepower Threat Defense, or Secure Firewall Management Center) and its version number.
    Affected if The product is any Cisco Firepower product and the version matches 'all versions' for Firepower Services for ASA or Firepower Threat Defense, or versions 2.9.13, 2.9.14.0, or 3.0.0 for Secure Firewall Management Center.
  2. Verify HTTP traffic filtering is enabled
    In Firepower Management Center, navigate to Policies > Access Control > HTTP Policy or check the active Access Control Policy to confirm HTTP/S traffic filtering rules are configured and the policy is applied to the target devices.
    Affected if HTTP traffic filtering is enabled and the device is actively inspecting HTTP or HTTPS traffic, as the bypass only affects filtered traffic.
  3. Confirm the device is processing HTTP traffic
    Check the Firepower dashboard or use 'show conn' in the CLI to verify the device is actively processing HTTP or HTTPS connections that would be subject to filtering rules.
    Affected if The device is processing HTTP/HTTPS traffic that should be filtered by Firepower policies.
  4. Compare installed version to affected ranges
    Compare your identified version from step 1 against the affected ranges: Firepower Services for ASA (all versions), Firepower Threat Defense (all versions), Secure Firewall Management Center (=2.9.13, =2.9.14.0, =3.0.0).
    Affected if The installed version falls within the affected ranges for any of the three products listed.

If you are running any Cisco Firepower product with HTTP filtering enabled and your version matches the affected ranges (all versions for Firepower Services for ASA and Firepower Threat Defense, or versions 2.9.13, 2.9.14.0, 3.0.0 for Secure Firewall Management Center), your environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco vendor patches/updates for Firepower Threat Defense, FirePOWER Services for ASA, and Firepower Management Center to fix the improper HTTP header handling in the filtering component.

Fix this in Firepower Services Software For Asa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1982 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data