# CVE-2015-4047: Null dereference in n/a

> Remote attackers can crash the IKE daemon via crafted UDP requests, causing denial of service in IPsec-Tools.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DLA-234-1, DSA-3272-1, GHSA-47jj-2hp6-grww, MGASA-2015-0243, SUSE-SU-2015:1367-1, UBUNTU-CVE-2015-4047

## What is CVE-2015-4047?

CVE-2015-4047 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 29 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

racoon/gssapi.c in IPsec-Tools 0.8.2 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon crash) via a series of crafted UDP requests.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2015-4047?

It affects 25 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ipsec-tools` | SUSE:Linux Enterprise Server 11 SP3 | All versions | 0.7.3-1.13.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 0.7.3-1.13.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 0.7.3-1.13.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server for SAP Applications 11 SP3 | All versions | 0.7.3-1.13.1 |
| `ipsec-tools` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 0.7.3-1.13.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Domain Name System, F5 Big-Ip Edge Gateway, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Protocol Security Manager, F5 Big-Ip Wan Optimization Manager, F5 Big-Ip Webaccelerator, F5 Big-Iq Adc, F5 Big-Iq Centralized Management, F5 Big-Iq Cloud, F5 Big-Iq Cloud and Orchestration and 5 more.

## How do I fix CVE-2015-4047?

Apply the vendor's patch.

## Is CVE-2015-4047 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4047 and fix it if it is affected.

What it is: CVE-2015-4047 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 29 May 2015. 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-2015-4047 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2015-4047/ (Markdown: https://insights.sbomify.com/CVE-2015-4047/index.md)
```

## Sources

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

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