Skip to content
Fencer Intel
high 7.8

CVE-2017-11464 json

A SIGFPE is raised in the function box_blur_line of rsvg-filter.c in GNOME librsvg 2.40.17 during an attempted parse of a crafted SVG file,…

published 2017-07-19 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3085

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

Summary

A SIGFPE is raised in the function box_blur_line of rsvg-filter.c in GNOME librsvg 2.40.17 during an attempted parse of a crafted SVG file, because of incorrect protection against division by zero.

Patch / fix

  • librsvg Debian 14, Debian 13, Debian 12 2.40.18-1

debian advisories DEBIAN-CVE-2017-11464

  • librsvg Ubuntu 16.04 LTS 2.40.13-3ubuntu0.1

ubuntu advisories UBUNTU-CVE-2017-11464

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

  • librsvg SLES for SAP 12 SP3, SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2 +6 more 2.40.18-5.3.1

suse advisories SUSE-SU-2017:2117-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-2017-11464 updated cvss 3.3

librsvg: SIGFPE is raised in box_blur_line function of rsvg-filter.c

  • Red Hat Enterprise Linux 5 librsvg2 Red Hat Enterprise Linux 6 librsvg2 Red Hat Enterprise Linux 7 librsvg2, librsvg2-tools
    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

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

CVSS scores

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