{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57811 exists.","fix":"No fix has been published for CVE-2024-57811 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57811 is a critical vulnerability in n/a, published on 13 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 CVE-2024-57811 and fix it if it is affected.\n\nWhat it is: CVE-2024-57811 is a critical vulnerability in n/a, published on 13 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57811 exists.\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-2024-57811/ (Markdown: https://insights.sbomify.com/CVE-2024-57811/index.md)","id":"CVE-2024-57811","markdown":"https://insights.sbomify.com/CVE-2024-57811/index.md","name":"CVE-2024-57811","record":{"aliases":[],"analysis":{"component_type":"ics_ot","fix_type":"end_of_life","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Eaton XC-303 PLC","requires_auth":"none","summary":"Attackers can gain root access to Eaton XC-303 PLCs via SSH using hardcoded credentials, posing a critical risk to industrial control systems.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"In Eaton X303 3.5.16 - X303 3.5.17 Build 712, an attacker with network access to a XC-303 PLC can login as root over SSH. The root password is hardcoded in the firmware. NOTE: This vulnerability appears in versions that are no longer supported by Eaton.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-57811","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Raptor RDF Syntax Library","id":"CVE-2024-57822"},"packages":[],"prev":{"headline":"PCI: imx6: Fix suspend/resume support on i.MX6QDL","id":"CVE-2024-57809"},"products":["n/a"],"published":"2025-01-13","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-16","vendors":["n/a"]},"summary":"Attackers can gain root access to Eaton XC-303 PLCs via SSH using hardcoded credentials, posing a critical risk to industrial control systems.","url":"https://insights.sbomify.com/CVE-2024-57811/"}