Skip to content
Fencer Intel
critical 9.8

CVE-2014-9474 json

Buffer overflow in the mpfr_strtofr function in GNU MPFR before 3.1.2-p11 allows context-dependent attackers to have unspecified impact via…

published 2017-10-09 9 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9293

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

Summary

Buffer overflow in the mpfr_strtofr function in GNU MPFR before 3.1.2-p11 allows context-dependent attackers to have unspecified impact via vectors related to incorrect documentation for mpn_set_str.

Patch / fix

  • mpfr4 Debian 14, Debian 13, Debian 12 3.1.2-2

debian advisories DEBIAN-CVE-2014-9474

  • mpfr RHEL 7 ELS 3.1.1-4.el7_9.2

red hat advisories RHSA-2025:9332

  • mpfr openSUSE Tumbleweed 3.1.5-2.1

opensuse advisories openSUSE-SU-2024:10472-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-2014-9474 updated cvss 7.0

mpfr: buffer overflow in mpfr_strtofr

  • Red Hat Enterprise Linux 6 mpfr
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Server (v. 7 ELS) mpfr 3.1.1-4.el7_9.2
    fixed: vendor fix RHSA-2025:9332

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

4.55% chance of exploitation in the next 30 days, higher than 91% 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
  • 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.