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

> Remote attackers can cause denial of service on Cisco ASA devices via HTTPS packet floods, requiring an upgrade to the security module.

- **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:** 9 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cqpv-62w6-mhqp

## What is CVE-2016-1312?

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

### Official description

The HTTPS inspection engine in the Content Security and Control Security Services Module (CSC-SSM) 6.6 before 6.6.1164.0 for Cisco ASA 5500 devices allows remote attackers to cause a denial of service (memory consumption or device reload) via a flood of HTTPS packets, aka Bug ID CSCue76147.

Weakness: CWE-399, CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Cisco Asa 5500 Csc-Ssm Firmware.

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

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

## Is CVE-2016-1312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1312 is a high-severity denial of service vulnerability in n/a, published on 9 Mar 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-1312 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-1312/ (Markdown: https://insights.sbomify.com/CVE-2016-1312/index.md)
```

## Sources

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

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