Skip to content
Fencer Intel
medium 4.5

CVE-2014-1934 json

eyeD3 is vulnerable to arbitrary file modification via symlink attack

published 12y ago modified 4mo ago also GHSA-4r2w-w73w-36jm , PYSEC-2026-807 , EUVD-2022-2435

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

Summary

tag.py in eyeD3 (aka python-eyed3) 7.0.3, 0.6.18, and earlier for Python allows local users to modify arbitrary files via a symlink attack on a temporary file.

Patch / fix

  • pypi eyed3 0.7.5
  • eyed3 Debian 14, Debian 13, Debian 12 0.6.18-3

debian advisories DEBIAN-CVE-2014-1934

  • python-eyeD3 openSUSE Tumbleweed 0.7.4-3.3

opensuse advisories openSUSE-SU-2024:10474-1

Is CVE-2014-1934 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-1934 updated cvss 2.1

python-eyed3: insecure temporary file creation

  • 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.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi eyed3
<0.7.5
0.7.5

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.