Creation of Temporary File With Insecure Permissions in logilab-commons
The Execute class in shellutils in logilab-common before 0.61.0 uses tempfile.mktemp, which allows local users to have an unspecified impact by pre-creating the temporary file.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | logilab-common | < 0.61.0 | 0.61.0 |
References
- http://lists.opensuse.org/opensuse-updates/2014-02/msg00085.html
- http://www.logilab.org/ticket/207562
- http://secunia.com/advisories/57209
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737051
- http://comments.gmane.org/gmane.comp.security.oss.general/11986
- https://github.com/advisories/GHSA-g5m2-22h2-rr3j
- https://nvd.nist.gov/vuln/detail/CVE-2014-1839
- https://github.com/pypa/advisory-database/tree/main/vulns/logilab-common/PYSEC-2014-84.yaml
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L- Weakness (CWE)
CWE-378- Platform
- Python (PyPI)
- Package
logilab-common- Disclosed
- 11.03.2014
- Updated
- 11.10.2026 11:20
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2014-84 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-g5m2-22h2-rr3j - CC BY 4.0
Vulnerability history: logilab-common
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 2
- First → latest
- 03.2014 03.2014
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 1
- Medium 1
Disclosures per year
- 2017: 0
- 2018: 0
- 2019: 0
- 2020: 0
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
earlier: 2
-
Creation of Temporary File With Insecure Permissions in logilab-commons this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.