Skip to content
Fencer Intel
low 3.3

CVE-2014-2524 json

The _rl_tropen function in util.c in GNU readline before 6.3 patch 3 allows local users to create or overwrite arbitrary files via a symlin…

published 12y ago modified 4mo ago also EUVD-2014-2560

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

Summary

The _rl_tropen function in util.c in GNU readline before 6.3 patch 3 allows local users to create or overwrite arbitrary files via a symlink attack on a /var/tmp/rltrace.[PID] file.

Patch / fix

  • bash openSUSE Tumbleweed 7.0-92.1
  • crash openSUSE Tumbleweed 7.1.5_k4.8.13_1-3.51

opensuse advisories openSUSE-SU-2024:10106-1openSUSE-SU-2024:10111-1

Is CVE-2014-2524 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-2014-2524 updated cvss 2.1

readline: insecure temporary file use in _rl_tropen()

  • Red Hat Enterprise Linux 6 readline
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 readline, compat-readline43 Red Hat Enterprise Linux 6 compat-readline5, mingw32-readline Red Hat Enterprise Linux 7 readline
    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

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

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.