{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41579 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41579 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41579 is a high-severity path traversal vulnerability in n/a, published on 4 Oct 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-41579 and fix it if it is affected.\n\nWhat it is: CVE-2021-41579 is a high-severity path traversal vulnerability in n/a, published on 4 Oct 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-41579 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-41579/ (Markdown: https://insights.sbomify.com/CVE-2021-41579/index.md)","id":"CVE-2021-41579","markdown":"https://insights.sbomify.com/CVE-2021-41579/index.md","name":"CVE-2021-41579","record":{"aliases":["GHSA-q78c-pv4h-fqw6"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SCADA software","requires_auth":"none","summary":"Attackers can bypass consent popups and write arbitrary files via malicious project files, leading to code execution in LAquis SCADA.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"scada","vendor":"laquisscada"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"LCDS LAquis SCADA through 4.3.1.1085 is vulnerable to a control bypass and path traversal. If an attacker can get a victim to load a malicious els project file and use the play feature, then the attacker can bypass a consent popup and write arbitrary files to OS locations where the user has permission, leading to code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-02-12","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-02-12T03:02:41Z","kind":"github_poc","ref":"https://github.com/mbanyamer/CVE-2021-41579-LCDS-LAquis-SCADA-4.3.1.1085-Arbitrary-File-Write","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2021-41579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Access Control in passport-oauth2","id":"CVE-2021-41580"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2021-41578"},"products":["n/a"],"published":"2021-10-04","related":[{"cvss_score":7.8,"headline":"Memory corruption in LAquis SCADA","id":"CVE-2020-25188","kev_date_added":null,"published":"2020-10-14"},{"cvss_score":7.8,"headline":"Memory corruption in LCDS LAquis SCADA","id":"CVE-2019-10980","kev_date_added":null,"published":"2019-08-05"},{"cvss_score":3.3,"headline":"Information disclosure in LCDS LAquis SCADA","id":"CVE-2019-10994","kev_date_added":null,"published":"2019-08-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass consent popups and write arbitrary files via malicious project files, leading to code execution in LAquis SCADA.","url":"https://insights.sbomify.com/CVE-2021-41579/"}