# CVE-2016-5561: Unspecified vulnerability in Oracle Sun Solaris 11.3 allows remote attackers to affect availability via vectors related to IKE.


- **Severity:** Low 3.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-9fcx-97mc-w45h

## What is CVE-2016-5561?

CVE-2016-5561 is a low-severity vulnerability in Oracle Solaris, published on 25 Oct 2016. 

### Official description

Unspecified vulnerability in Oracle Sun Solaris 11.3 allows remote attackers to affect availability via vectors related to IKE.

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

It affects 1 product.


Products: Oracle Solaris.

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

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

## Is CVE-2016-5561 being exploited?

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

## Other vulnerabilities in Oracle Solaris

- [CVE-2020-14871](https://insights.sbomify.com/CVE-2020-14871/): Oracle Solaris and Zettabyte File System (ZFS) Unspecified (critical 10.0, exploited in the wild)
- [CVE-2019-3010](https://insights.sbomify.com/CVE-2019-3010/): Oracle Solaris Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2026-46978](https://insights.sbomify.com/CVE-2026-46978/): Missing authorization in Oracle Solaris (critical 10.0)
- [CVE-2017-3623](https://insights.sbomify.com/CVE-2017-3623/): Other in Solaris Operating System (critical 10.0)
- [CVE-2014-0397](https://insights.sbomify.com/CVE-2014-0397/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5561 is a low-severity vulnerability in Oracle Solaris, published on 25 Oct 2016. 
Exploitation: There is no known exploitation of CVE-2016-5561 in the wild and no public exploit code.

Affected product: Oracle Solaris. 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-5561/ (Markdown: https://insights.sbomify.com/CVE-2016-5561/index.md)
```

## Sources

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

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