Skip to content
Fencer Intel
medium 5.1

CVE-2015-1865 json

fts.c in coreutils 8.4 allows local users to delete arbitrary files.

published 9y ago modified 4mo ago also EUVD-2015-1972

cvss
5.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

fts.c in coreutils 8.4 allows local users to delete arbitrary files.

Patch / fix

  • coreutils Debian 14, Debian 13, Debian 12 8.13-1

debian advisories DEBIAN-CVE-2015-1865

Is CVE-2015-1865 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-2015-1865 updated cvss 2.6

coreutils: "time of check to time of use" race condition fts.c

  • Red Hat Enterprise Linux 5 coreutils Red Hat Enterprise Linux 6 coreutils, coreutils-libs
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 coreutils
    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

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

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

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA 3.1 5.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.0 4.7 CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

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.