Skip to content
Fencer Intel
medium 5.5

CVE-2014-1859 json

Numpy arbitrary file write via symlink attack

published 2018-01-08 8 y ago modified 2026-06-17 4 mo ago also GHSA-2fc2-6r4j-p65h , PYSEC-2018-34 , EUVD-2018-0108

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

Summary

(1) core/tests/test_memmap.py, (2) core/tests/test_multiarray.py, (3) f2py/f2py2e.py, and (4) lib/tests/test_io.py in NumPy before 1.8.1 allow local users to write to arbitrary files via a symlink attack on a temporary file.

Patch / fix

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-1859 updated cvss 2.1

numpy: f2py insecure temporary file use

  • Red Hat OpenShift Enterprise 1 numpy Red Hat Enterprise Linux 6 numpy, numpy-f2py Red Hat Enterprise Linux 7 numpy, numpy-f2py Red Hat Enterprise MRG 1 numpy Red Hat OpenShift Enterprise 2 python27-numpy Red Hat Software Collections python27-numpy, python33-numpy, python27-numpy-f2py, python33-numpy-f2py
    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

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

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi numpy
<1.8.1
1.8.1

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.