dbcve.org
Asa With Firepower ServicesApplication · Cisco

CVE-2016-1345

HIGH · 7.5 CVSS v3.0 Published 2016-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Cisco FireSIGHT System Software 5.4.0 through 6.0.1 and ASA with FirePOWER Services 5.4.0 through 6.0.0.1 allow remote attackers to bypass malware protection via crafted fields in HTTP headers, aka Bug ID CSCux22726.

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 · high confidence

The vulnerability exists in Cisco FireSIGHT System Software (5.4.0-6.0.1) and ASA with FirePOWER Services (5.4.0-6.0.0.1). Attackers can bypass the malware detection engine by embedding malicious content within crafted HTTP header fields, allowing malware to traverse the security appliance undetected.

MitigationApply the vendor patch by upgrading to versions beyond 6.0.1 (FireSIGHT) and 6.0.0.1 (ASA FirePOWER). If immediate patching is not feasible, implement supplemental HTTP traffic inspection and filtering at upstream perimeter devices to detect header-based evasion attempts.

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
Asa With Firepower ServicesApplication
Affected:= 5.4.0= 5.4.0.1= 5.4.0.2= 5.4.0.3= 5.4.0.4= 5.4.0.5= 5.4.0.6= 6.0.0= 6.0.0.1
Firesight System SoftwareApplication
Affected:= 5.4.0= 5.4.0.1= 5.4.0.2= 5.4.0.3= 5.4.0.4= 5.4.0.5= 5.4.0.6= 5.4.1= 5.4.1.2= 5.4.1.3= 5.4.1.4= 6.0.0

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
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 product
    Log into the device CLI or management console and run 'show version' or check the system dashboard to determine if the device runs FireSIGHT System Software or ASA with FirePOWER Services
    Affected if The device is running either Cisco FireSIGHT System Software or Cisco ASA with FirePOWER Services
  2. Check the software version
    Run 'show version' on the device CLI or view the version in the management interface. Compare the version number against the affected ranges: FireSIGHT 5.4.0 through 6.0.1, or ASA FirePOWER 5.4.0 through 6.0.0.1
    Affected if The installed version matches any of: 5.4.0, 5.4.0.1, 5.4.0.2, 5.4.0.3, 5.4.0.4, 5.4.0.5, 5.4.0.6, 5.4.1, 5.4.1.2, 5.4.1.3, 5.4.1.4, 6.0.0, or 6.0.0.1 for ASA FirePOWER
  3. Verify malware detection inspection is enabled
    Check the intrusion policy configuration in the FireSIGHT/ASA FirePOWER management interface, or run 'show policy-map' and look for intrusion policy with malware detection/Snort inspection applied to HTTP traffic
    Affected if An intrusion policy with malware detection is actively applied to traffic inspection
  4. Confirm HTTP traffic inspection is active
    Run 'show service-policy' to verify HTTP inspection is enabled on the relevant interfaces, or check the access policy in the management console to confirm traffic is being inspected
    Affected if HTTP traffic inspection is enabled and the device is actively inspecting HTTP header fields

You are affected if your device runs FireSIGHT System Software version 5.4.0-6.0.1 or ASA with FirePOWER Services version 5.4.0-6.0.0.1 and has malware detection inspection enabled for HTTP traffic.

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 the vendor patch by upgrading to versions beyond 6.0.1 (FireSIGHT) and 6.0.0.1 (ASA FirePOWER). If immediate patching is not feasible, implement supplemental HTTP traffic inspection and filtering at upstream perimeter devices to detect header-based evasion attempts.

Fix this in Asa With Firepower Services Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1345 — 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-2016-1345 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