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

> Remote attackers can exhaust computational resources in the racoon daemon by sending specially crafted ISAKMP fragment packets, causing a denial of service.

- **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:** Yes
- **Published:** 6 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DLA-1044-1, GHSA-575v-phrx-cjcp, SUSE-SU-2018:0423-1, SUSE-SU-2018:0424-1, UBUNTU-CVE-2016-10396

## What is CVE-2016-10396?

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

### Official description

The racoon daemon in IPsec-Tools 0.8.2 contains a remotely exploitable computational-complexity attack when parsing and storing ISAKMP fragments. The implementation permits a remote attacker to exhaust computational resources on the remote endpoint by repeatedly sending ISAKMP fragment packets in a particular order such that the worst-case computational complexity is realized in the algorithm utilized to determine if reassembly of the fragments can take place.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ipsec-tools` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 0.7.3-1.38.3.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 0.8.0-19.3.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 0.8.0-19.3.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 0.8.0-19.3.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 0.7.3-1.38.3.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 0.8.0-19.3.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 0.8.0-19.3.1 |

Products: Ipsec-Tools Ipsec-Tools.

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

Apply the vendor's patch.

## Is CVE-2016-10396 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0607](https://insights.sbomify.com/CVE-2004-0607/): Auth bypass in n/a (critical 10.0)
- [CVE-2008-3652](https://insights.sbomify.com/CVE-2008-3652/): Denial of service in n/a (high 7.8)
- [CVE-2005-3732](https://insights.sbomify.com/CVE-2005-3732/): Null dereference in n/a (high 7.8)
- [CVE-2009-1632](https://insights.sbomify.com/CVE-2009-1632/): Denial of service in n/a (medium 5.0)
- [CVE-2009-1574](https://insights.sbomify.com/CVE-2009-1574/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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