# CVE-2016-1369: Denial of service in n/a

> Remote attackers can cause denial of service on Cisco ASA FirePOWER modules by flooding crafted IP traffic due to kernel logging misconfiguration.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-65p4-8967-8v6f

## What is CVE-2016-1369?

CVE-2016-1369 is a high-severity denial of service vulnerability in n/a, published on 5 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Adaptive Security Appliance (ASA) 5585-X FirePOWER Security Services Processor (SSP) module for Cisco ASA with FirePOWER Services 5.3.1 through 6.0.0 misconfigures kernel logging, which allows remote attackers to cause a denial of service (resource consumption, and inspection outage or module outage) via a flood of crafted IP traffic, aka Bug ID CSCux19922.

Weakness: CWE-399

## Which versions are affected by CVE-2016-1369?

It affects 1 product.


Products: Cisco Asa With Firepower Services.

## How do I fix CVE-2016-1369?

No fix has been published for CVE-2016-1369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-1369 being exploited?

There is no known exploitation of CVE-2016-1369 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-1345](https://insights.sbomify.com/CVE-2016-1345/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1369 and fix it if it is affected.

What it is: CVE-2016-1369 is a high-severity denial of service vulnerability in n/a, published on 5 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1369 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1369/ (Markdown: https://insights.sbomify.com/CVE-2016-1369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1369
- OSV: https://osv.dev/vulnerability/CVE-2016-1369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1369/
Summaries are generated and may contain mistakes; the official description above is the record.