How severe is CVE-2014-1624?

CVE-2014-1624 has a CVSS 2.0 base score of 3.3, rated low severity.

Is CVE-2014-1624 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2014-1624?

CVE-2014-1624 affects Python Pyxdg. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2014-1624?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2014-1624 published?

CVE-2014-1624 was published on 2014-01-28 and last updated on 2026-06-17.

CVE-2014-1624

CVE-2014-1624 is a low-severity vulnerability in Python Pyxdg with a CVSS 2.0 base score of 3.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-59.

Key facts

Severity: Low (CVSS 2.0 base score 3.3)
EPSS exploit prediction: 0% (23rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-59
Affected product: Python Pyxdg
Published: 2014-01-28
Last modified: 2026-06-17

Description

Race condition in the xdg.BaseDirectory.get_runtime_dir function in python-xdg 0.25 allows local users to overwrite arbitrary files by pre-creating /tmp/pyxdg-runtime-dir-fallback-victim to point to a victim-owned location, then replacing it with a symlink to an attacker-controlled location once the get_runtime_dir function is called.

Frequently asked questions

What is CVE-2014-1624?: Race condition in the xdg.BaseDirectory.get_runtime_dir function in python-xdg 0.25 allows local users to overwrite arbitrary files by pre-creating /tmp/pyxdg-runtime-dir-fallback-victim to point to a victim-owned location, then replacing it with a symlink to an attacker-controlled location once the get_runtime_dir function is called.
How severe is CVE-2014-1624?: CVE-2014-1624 has a CVSS 2.0 base score of 3.3, rated low severity.
Is CVE-2014-1624 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2014-1624?: CVE-2014-1624 affects Python Pyxdg. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2014-1624?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2014-1624 published?: CVE-2014-1624 was published on 2014-01-28 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:python:pyxdg:0.25:*:*:*:*:*:*:*

More vulnerabilities in Python Pyxdg

CVE-2019-12761 — High (CVSS 7.5): A code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML…

All CVEs affecting Python Pyxdg →

Other CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities

CVE-2024-37143 — Critical (CVSS 10.0): Dell PowerFlex appliance versions prior to IC 46.381.00 and IC 46.376.00, Dell PowerFlex rack versions prior to RCM…
CVE-2024-28189 — Critical (CVSS 10.0): Judge0 is an open-source online code execution system. The application uses the UNIX chown command on an untrusted file…
CVE-2024-28185 — Critical (CVSS 10.0): Judge0 is an open-source online code execution system. The application does not account for symlinks placed inside the…
CVE-2022-22995 — Critical (CVSS 10.0): The combination of primitives offered by SMB and AFP in their default configuration allows the arbitrary writing of…
CVE-2014-4480 — Critical (CVSS 10.0): Directory traversal vulnerability in afc in AppleFileConduit in Apple iOS before 8.1.3 and Apple TV before 7.0.3 allows…
CVE-2002-2374 — Critical (CVSS 10.0): Unspecified vulnerability in pprosetup in Sun PatchPro 2.0 has unknown impact and attack vectors related to "unsafe use…

Browse all CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities →