{"answers":{"affected":"3 open source packages ship an affected version, including basicsr.","exploited":"There is no known exploitation of CVE-2024-27763 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-27763 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-27763 is a medium-severity command injection vulnerability in n/a, published on 12 Mar 2025. 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-2024-27763 and fix it if it is affected.\n\nWhat it is: CVE-2024-27763 is a medium-severity command injection vulnerability in n/a, published on 12 Mar 2025. 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-2024-27763 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- basicsr (PyPI): affected all versions up to 1.4.2; no fix listed\n- basicsr (PyPI): affected all versions up to 1.4.2; no fix listed\n- basicsr (PyPI): affected all versions up to 1.4.2; 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/CVE-2024-27763/ (Markdown: https://insights.sbomify.com/CVE-2024-27763/index.md)","id":"CVE-2024-27763","markdown":"https://insights.sbomify.com/CVE-2024-27763/index.md","name":"CVE-2024-27763","record":{"aliases":["GHSA-86w8-vhw6-q9qq","PYSEC-2026-1215"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Python image processing library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code via a crafted SLURM_NODELIST environment variable when scontrol is invoked.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"XPixelGroup BasicSR through 1.4.2 might locally allow code execution in contrived situations where \"scontrol show hostname\" is executed in the presence of a crafted SLURM_NODELIST environment variable.","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":false,"headline":"XPixelGroup BasicSR Command Injection","id":"CVE-2024-27763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2024-27764"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.4.2"],"package":"basicsr","purl":null,"source":"GHSA-86w8-vhw6-q9qq"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.4.2"],"package":"basicsr","purl":"pkg:pypi/basicsr","source":"GHSA-86w8-vhw6-q9qq"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.4.2"],"package":"basicsr","purl":"pkg:pypi/basicsr","source":"PYSEC-2026-1215"}],"prev":{"headline":"RPyC's missing security check results in code execution when using numpy.array on the server-side.","id":"CVE-2024-27758"},"products":["n/a"],"published":"2025-03-12","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-12","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via a crafted SLURM_NODELIST environment variable when scontrol is invoked.","url":"https://insights.sbomify.com/CVE-2024-27763/"}