{"answers":{"affected":"1 open source package ship an affected version, including ctx.","exploited":"There is no known exploitation of PYSEC-2022-199 in the wild and no public exploit code.","fix":"No fix has been published for PYSEC-2022-199 yet. Limit exposure of the affected software until one is available.","what":"PYSEC-2022-199 is a vulnerability in ctx, published on 24 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for PYSEC-2022-199 and fix it if it is affected.\n\nWhat it is: PYSEC-2022-199 is a vulnerability in ctx, published on 24 May 2022. 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-2022-199 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ctx (PyPI): affected from 0.1.2-1; 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-199/ (Markdown: https://insights.sbomify.com/PYSEC-2022-199/index.md)","id":"PYSEC-2022-199","markdown":"https://insights.sbomify.com/PYSEC-2022-199/index.md","name":"PYSEC-2022-199","record":{"aliases":["GSD-2022-1002521"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python package","requires_auth":"none","summary":"A backdoor in the ctx Python package allows attackers to steal credentials from environment variables via malicious updates.","user_interaction":"not_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":"In PyPI ctx version 0.1.2-1, 0.1.2-2, 0.1.4, 0.2, 0.2.1, 0.2.2, 0.2.2.1, 0.2.3, 0.2.4, 0.2.5, 0.2.6 a backdoor exists in the ctx package that can be attacked via a malicious package update resulting in credential theft from environment variables","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":"backdoor in ctx version 0.1.2-1, 0.1.2-2, 0.1.4, 0.2, 0.2.1, 0.2.2, 0.2.2.1, 0.2.3, 0.2.4, 0.2.5, 0.2.6","id":"PYSEC-2022-199","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":["0.1.2-1"],"last_affected":[],"package":"ctx","purl":"pkg:pypi/ctx","source":"PYSEC-2022-199"}],"products":null,"published":"2022-05-24","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":"A backdoor in the ctx Python package allows attackers to steal credentials from environment variables via malicious updates.","url":"https://insights.sbomify.com/PYSEC-2022-199/"}