{"answers":{"affected":"1 open source package ship an affected version, including uniapi.","exploited":"There is no known exploitation of PYSEC-2025-2 in the wild and no public exploit code.","fix":"No fix has been published for PYSEC-2025-2 yet. Limit exposure of the affected software until one is available.","what":"PYSEC-2025-2 is a vulnerability in uniapi, published on 24 Jan 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-2 and fix it if it is affected.\n\nWhat it is: PYSEC-2025-2 is a vulnerability in uniapi, published on 24 Jan 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-2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- uniapi (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-2/ (Markdown: https://insights.sbomify.com/PYSEC-2025-2/index.md)","id":"PYSEC-2025-2","markdown":"https://insights.sbomify.com/PYSEC-2025-2/index.md","name":"PYSEC-2025-2","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python library","requires_auth":"none","summary":"Malicious code in the uniapi library harvests system information and executes remote scripts upon import, requiring users to upgrade to a safe version.","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":"uniapi version 1.0.7 introduces code that would execute\non import of the module and download a script from a remote URL,\nand would then execute the downloaded script in a thread.\nThe downloaded script would harvest system information\nand `POST` the information to another remote URL.\nThis code was found in the PyPI release artifacts and was not present\nin the public GitHub repository.","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":"uniapi version 1.0.7 contained an information harvesting script.","id":"PYSEC-2025-2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"uniapi","purl":"pkg:pypi/uniapi","source":"PYSEC-2025-2"}],"products":null,"published":"2025-01-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":"Malicious code in the uniapi library harvests system information and executes remote scripts upon import, requiring users to upgrade to a safe version.","url":"https://insights.sbomify.com/PYSEC-2025-2/"}