Skip to content
Fencer Intel
critical 9.8

CVE-2015-5224 json

The mkostemp function in login-utils in util-linux when used incorrectly allows remote attackers to cause file name collision and possibly…

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

cvss
9.8
version 3.1, CNA
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

The mkostemp function in login-utils in util-linux when used incorrectly allows remote attackers to cause file name collision and possibly other attacks.

Patch / fix

  • util-linux Debian 14, Debian 13, Debian 12 2.27-1

debian advisories DEBIAN-CVE-2015-5224

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

util-linux: File name collision due to incorrect mkstemp use

  • Red Hat Enterprise Linux 5 util-linux Red Hat Enterprise Linux 6 uuidd, libuuid, libblkid, util-linux-ng Red Hat Enterprise Linux 7 uuidd, libuuid, libblkid, libmount, util-linux
    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
none
Automatable
yes
Technical impact
total
Assessed
11mo ago

Exploit prediction

4.53% 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
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/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-377 DEPRECATED: Insecure Temporary File

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.