# CVE-2016-4912: Null dereference in n/a

> Remote attackers can crash the OpenSLP server by sending crafted packets that trigger a NULL pointer dereference during memory allocation.

- **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:** 27 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-36966, AZL-7319, GHSA-m4qh-6ff4-g5xx, MGASA-2016-0222

## What is CVE-2016-4912?

CVE-2016-4912 is a high-severity vulnerability in n/a, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The _xrealloc function in xlsp_xmalloc.c in OpenSLP 2.0.0 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via a large number of crafted packets, which triggers a memory allocation failure.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Openslp Openslp.

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

Apply the vendor's patch.

## Is CVE-2016-4912 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-7567](https://insights.sbomify.com/CVE-2016-7567/): Memory corruption in n/a (critical 9.8)
- [CVE-2005-0769](https://insights.sbomify.com/CVE-2005-0769/): Memory corruption in n/a (high 7.5)
- [CVE-2010-3609](https://insights.sbomify.com/CVE-2010-3609/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0875](https://insights.sbomify.com/CVE-2003-0875/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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