Skip to content
Fencer Intel
high 7.5

CVE-2016-10325 json

In libosip2 in GNU oSIP 4.1.0, a malformed SIP message can lead to a heap buffer overflow in the _osip_message_to_str() function defined in…

published 2017-04-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1509

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

Summary

In libosip2 in GNU oSIP 4.1.0, a malformed SIP message can lead to a heap buffer overflow in the _osip_message_to_str() function defined in osipparser2/osip_message_to_str.c, resulting in a remote DoS.

Patch / fix

  • libosip2 Debian 14, Debian 13, Debian 12 4.1.0-2.1

debian advisories DEBIAN-CVE-2016-10325

  • libosip2 Ubuntu 16.04 LTS 4.1.0-2+deb8u1build0.16.04.1

ubuntu advisories UBUNTU-CVE-2016-10325

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libosip2 SLED 12 SP2, SLED 12 SP1, SLE Workstation Extension 12 SP2 +3 more 3.5.0-20.1
  • libosip2 SLE Software Development Kit 11 SP4 3.1.0-3.1

suse advisories SUSE-SU-2017:1187-1SUSE-SU-2017:1188-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-10325 updated

libosip2: Multiple vulnerabilities

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

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

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
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.