{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-27593 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27593 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27593 is a critical code injection vulnerability in SICK DL100-2xxxxxxx, published on 14 Mar 2025. 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 CVE-2025-27593 and fix it if it is affected.\n\nWhat it is: CVE-2025-27593 is a critical code injection vulnerability in SICK DL100-2xxxxxxx, published on 14 Mar 2025. 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 CVE-2025-27593 in the wild and no public exploit code.\n\nAffected product: SICK DL100-2xxxxxxx. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-27593/ (Markdown: https://insights.sbomify.com/CVE-2025-27593/index.md)","id":"CVE-2025-27593","markdown":"https://insights.sbomify.com/CVE-2025-27593/index.md","name":"CVE-2025-27593","record":{"aliases":["GHSA-jqv5-4r34-g3x7"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial sensor","requires_auth":"none","summary":"Attackers can execute arbitrary code on SICK DL100 sensors by distributing malicious device drivers due to missing download verification.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SICK AG","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"The product can be used to distribute malicious code using SDD Device Drivers due to missing download verification checks, leading to code execution on target systems.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"RCE due to Device Driver","id":"CVE-2025-27593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"Unencrypted transmission of password hash","id":"CVE-2025-27594"},"packages":[],"prev":{"headline":"Below has Incorrect Permission Assignment for Critical Resource","id":"CVE-2025-27591"},"products":["SICK DL100-2xxxxxxx"],"published":"2025-03-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-14","vendors":["SICK AG"]},"summary":"Attackers can execute arbitrary code on SICK DL100 sensors by distributing malicious device drivers due to missing download verification.","url":"https://insights.sbomify.com/CVE-2025-27593/"}