Skip to content
Fencer Intel
critical 9.8

CVE-2017-11125 json

libxar.so in xar 1.6.1 has a NULL pointer dereference in the xar_get_path function in util.c.

published 9y ago modified 4mo ago also EUVD-2017-2762

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

Summary

libxar.so in xar 1.6.1 has a NULL pointer dereference in the xar_get_path function in util.c.

Patch / fix

  • xar Debian 14, Debian 13 1.8.0.498-1

debian advisories DEBIAN-CVE-2017-11125

  • xar openSUSE Leap 16.0 1.8.0.0.503-bp160.1.1
  • xar openSUSE Tumbleweed 1.8.0.0.503-1.1

opensuse advisories openSUSE-SU-2026:21153-1openSUSE-SU-2026:11103-1

Is CVE-2017-11125 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2017-11125 updated cvss 3.3

xar: 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.95% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/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.