Skip to content
Fencer Intel
medium 5.6

CVE-2014-1839 json

Creation of Temporary File With Insecure Permissions in logilab-commons

published 12y ago modified 4mo ago also GHSA-g5m2-22h2-rr3j , PYSEC-2014-84 , EUVD-2014-0032

cvss
5.6
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

The Execute class in shellutils in logilab-commons before 0.61.0 uses tempfile.mktemp, which allows local users to have an unspecified impact by pre-creating the temporary file.

Patch / fix

  • pypi logilab-common 0.60.1, 0.61.0
  • logilab-common Debian 14, Debian 13, Debian 12 0.61.0-1

debian advisories DEBIAN-CVE-2014-1839

  • python-logilab-common openSUSE Tumbleweed 2.1.0-1.4
  • python-logilab-common openSUSE Tumbleweed 1.11.0-1.5

opensuse advisories openSUSE-SU-2026:12014-1openSUSE-SU-2024:14145-1

Is CVE-2014-1839 in your dependencies? 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-1839 updated cvss 3.3

python-logilab-common: multiple temporary file vulnerabilities

  • Red Hat All currently supported Red Hat products
    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.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.4 AV:L/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
pypi logilab-common
<0.61.0
<0.60.1
0.61.0
0.60.1

Classification

Weakness
  • CWE-378 Creation of Temporary File With Insecure Permissions

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.