Skip to content
Fencer Intel
high 7.5

CVE-2016-4912 json

The _xrealloc function in xlsp_xmalloc.c in OpenSLP 2.0.0 allows remote attackers to cause a denial of service (NULL pointer dereference an…

published 2017-03-27 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-5887

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.4%
EPSS 5.4% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

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.

Patch / fix

  • openslp SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +2 more 2.0.0-18.2.1
  • openslp SLES for SAP 12 SP1, SLES 12 SP1, SLED 12 SP1 +1 more 2.0.0-17.1

suse advisories SUSE-SU-2018:0100-1SUSE-SU-2016:2661-1

  • openslp openSUSE Tumbleweed 2.0.0-8.1

opensuse advisories openSUSE-SU-2024:10065-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-4912 updated cvss 5.4

openslp: null pointer dereference in _xrealloc() function

  • Red Hat Enterprise Linux 6 openslp, openslp-server Red Hat Enterprise Linux 7 openslp, openslp-server
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.36% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1329295 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.