{"answers":{"affected":"1 open source package ship an affected version, including deep-translator.","exploited":"There is no known exploitation of PYSEC-2022-252 in the wild and no public exploit code.","fix":"No fix has been published for PYSEC-2022-252 yet. Limit exposure of the affected software until one is available.","what":"PYSEC-2022-252 is a vulnerability in deep-translator, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for PYSEC-2022-252 and fix it if it is affected.\n\nWhat it is: PYSEC-2022-252 is a vulnerability in deep-translator, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of PYSEC-2022-252 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- deep-translator (PyPI): affected from 1.8.5; 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-2022-252/ (Markdown: https://insights.sbomify.com/PYSEC-2022-252/index.md)","id":"PYSEC-2022-252","markdown":"https://insights.sbomify.com/PYSEC-2022-252/index.md","name":"PYSEC-2022-252","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python translation library","requires_auth":"none","summary":"Attackers compromised the deep-translator PyPI account to inject malicious code that executes arbitrary commands and downloads malware during installation.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The deep-translator project on PyPI was taken over via user account compromise via a phishing attack and a new malicious release made which contained code which some environment variables and downloaded and ran malware at install time","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":"The deep-translator project on PyPI was taken over via user account compromise via a phishing attack and a new malicious release made which","id":"PYSEC-2022-252","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"supply_chain","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["1.8.5"],"last_affected":[],"package":"deep-translator","purl":"pkg:pypi/deep-translator","source":"PYSEC-2022-252"}],"products":null,"published":"2022-08-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":"Attackers compromised the deep-translator PyPI account to inject malicious code that executes arbitrary commands and downloads malware during installation.","url":"https://insights.sbomify.com/PYSEC-2022-252/"}