# CVE-2014-2037: Null dereference in n/a

> Remote attackers can cause a denial of service in Openswan by sending malformed IKEv2 packets, triggering a NULL pointer dereference and daemon restart.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4v68-wgfw-m69v

## What is CVE-2014-2037?

CVE-2014-2037 is a medium-severity vulnerability in n/a, published on 26 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads.  NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-2037?

It affects 1 product.


Products: Xelerance Openswan.

## How do I fix CVE-2014-2037?

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

## Is CVE-2014-2037 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15836](https://insights.sbomify.com/CVE-2018-15836/): Security feature bypass in n/a (high 7.5)
- [CVE-2013-2053](https://insights.sbomify.com/CVE-2013-2053/): Memory corruption in n/a (medium 6.8)
- [CVE-2010-3302](https://insights.sbomify.com/CVE-2010-3302/): Memory corruption in n/a (medium 6.5)
- [CVE-2010-3308](https://insights.sbomify.com/CVE-2010-3308/): Memory corruption in n/a (medium 6.5)
- [CVE-2010-3752](https://insights.sbomify.com/CVE-2010-3752/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2037 and fix it if it is affected.

What it is: CVE-2014-2037 is a medium-severity vulnerability in n/a, published on 26 Nov 2014. 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-2014-2037 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-2014-2037/ (Markdown: https://insights.sbomify.com/CVE-2014-2037/index.md)
```

## Sources

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

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