{"answers":{"affected":"1 open source package ship an affected version, including autodzee.","exploited":"There is no known exploitation of PYSEC-2025-3 in the wild and no public exploit code.","fix":"No fix has been published for PYSEC-2025-3 yet. Limit exposure of the affected software until one is available.","what":"PYSEC-2025-3 is a vulnerability in autodzee, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for PYSEC-2025-3 and fix it if it is affected.\n\nWhat it is: PYSEC-2025-3 is a vulnerability in autodzee, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of PYSEC-2025-3 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- autodzee (PyPI): affected all versions; no fix listed\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/PYSEC-2025-3/ (Markdown: https://insights.sbomify.com/PYSEC-2025-3/index.md)","id":"PYSEC-2025-3","markdown":"https://insights.sbomify.com/PYSEC-2025-3/index.md","name":"PYSEC-2025-3","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python music downloader","requires_auth":"none","summary":"The autodzee Python library exfiltrates user data to a hardcoded server, posing a privacy risk to users downloading music.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Published in 2019, the autodzee package is a Python library\nthat bypasses Deezer API restrictions to download music.\nThe package was found to exfiltrate user data to a hardcoded server,\nwhich could be used for malicious purposes.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"When using the project to bypass Deezer API restrictions, project exfiltrates user data to a hardcoded server.","id":"PYSEC-2025-3","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"autodzee","purl":"pkg:pypi/autodzee","source":"PYSEC-2025-3"}],"products":null,"published":"2025-02-26","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"The autodzee Python library exfiltrates user data to a hardcoded server, posing a privacy risk to users downloading music.","url":"https://insights.sbomify.com/PYSEC-2025-3/"}