{"answers":{"affected":"3 open source packages ship an affected version, including pillow. It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-1933 in the wild and no public exploit code.","fix":"Upgrade pillow to 2.3.1 or later.","what":"CVE-2014-1933 is a low-severity path traversal vulnerability in Python Pillow, published on 17 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-1933 and fix it if it is affected.\n\nWhat it is: CVE-2014-1933 is a low-severity path traversal vulnerability in Python Pillow, published on 17 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-1933 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pillow (PyPI): affected all versions; fixed in 2.3.1\n- pillow (PyPI): affected all versions; fixed in 2.3.1\n- pillow (PyPI): affected all versions; fixed in 2.3.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2014-1933/ (Markdown: https://insights.sbomify.com/CVE-2014-1933/index.md)","id":"CVE-2014-1933","markdown":"https://insights.sbomify.com/CVE-2014-1933/index.md","name":"CVE-2014-1933","record":{"aliases":["DEBIAN-CVE-2014-1933","GHSA-r854-96gq-rfg3","PYSEC-2014-23"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python image library","requires_auth":"low_privilege","summary":"Local attackers can exploit predictable temporary file names in PIL to perform symlink attacks, potentially reading or modifying arbitrary files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pillow","vendor":"python"},{"product":"python_imaging_library","vendor":"pythonware"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The (1) JpegImagePlugin.py and (2) EpsImagePlugin.py scripts in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 uses the names of temporary files on the command line, which makes it easier for local users to conduct symlink attacks by listing the processes.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Pillow Temporary file name leakage","id":"CVE-2014-1933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"python:pillow","products":["python:pillow"],"type":"path_traversal","year":"2014"},"n_packages":3,"n_references":7,"next":{"headline":"eyeD3 is vulnerable to arbitrary file modification via symlink attack","id":"CVE-2014-1934"},"packages":[{"ecosystem":"PyPI","fixed":["2.3.1"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":null,"source":"GHSA-r854-96gq-rfg3"},{"ecosystem":"PyPI","fixed":["2.3.1"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":"pkg:pypi/pillow","source":"GHSA-r854-96gq-rfg3"},{"ecosystem":"PyPI","fixed":["2.3.1"],"introduced":["0"],"last_affected":[],"package":"pillow","purl":"pkg:pypi/pillow","source":"PYSEC-2014-23"}],"prev":{"headline":"PIL and Pillow Vulnerable to Symlink Attack on Tmpfiles","id":"CVE-2014-1932"},"products":["n/a"],"published":"2014-04-17","related":[{"cvss_score":10,"headline":"Pillow command injection","id":"CVE-2014-3007","kev_date_added":null,"published":"2014-04-27"},{"cvss_score":9.8,"headline":"Pillow multi-frame loaders can reuse stale native image storage after mode transitions","id":"CVE-2026-96639","kev_date_added":null,"published":"2026-10-21"},{"cvss_score":9.8,"headline":"Buffer over-flow in Pillow","id":"CVE-2022-30595","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":9.8,"headline":"Out of bounds write in Pillow","id":"CVE-2021-25289","kev_date_added":null,"published":"2021-03-19"},{"cvss_score":9.8,"headline":"Pillow Integer overflow in ImagingResampleHorizontal","id":"CVE-2016-4009","kev_date_added":null,"published":"2016-04-13"},{"cvss_score":9.2,"headline":"Pillow: Heap buffer overflow in _tiffWriteProc when saving TIFF to BytesIO","id":"CVE-2026-112393","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":9.2,"headline":"Pillow: Heap buffer overflow in FlashPix (FPX) JPEG decoding leads to code execution","id":"CVE-2026-112398","kev_date_added":null,"published":"2026-10-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Local attackers can exploit predictable temporary file names in PIL to perform symlink attacks, potentially reading or modifying arbitrary files.","url":"https://insights.sbomify.com/CVE-2014-1933/"}