{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-52504 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-52504 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-52504 is a high-severity denial of service vulnerability in Siemens SIPROTEC 4 6MD61, published on 12 Aug 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-52504 and fix it if it is affected.\n\nWhat it is: CVE-2024-52504 is a high-severity denial of service vulnerability in Siemens SIPROTEC 4 6MD61, published on 12 Aug 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 CVE-2024-52504 in the wild and no public exploit code.\n\nAffected product: Siemens SIPROTEC 4 6MD61. 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-52504/ (Markdown: https://insights.sbomify.com/CVE-2024-52504/index.md)","id":"CVE-2024-52504","markdown":"https://insights.sbomify.com/CVE-2024-52504/index.md","name":"CVE-2024-52504","record":{"aliases":["GHSA-q8f8-8vf2-w978"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens SIPROTEC relay","requires_auth":"none","summary":"Unauthenticated remote attackers can cause a denial of service on Siemens SIPROTEC devices by interrupting file transfers, requiring a device restart to recover.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"A vulnerability has been identified in SIPROTEC 4 6MD61 (All versions), SIPROTEC 4 6MD63 (All versions), SIPROTEC 4 6MD66 (All versions), SIPROTEC 4 6MD665 (All versions), SIPROTEC 4 7SA522 (All versions), SIPROTEC 4 7SA6 (All versions \u003c V4.78), SIPROTEC 4 7SD5 (All versions \u003c V4.78), SIPROTEC 4 7SD610 (All versions \u003c V4.78), SIPROTEC 4 7SJ61 (All versions), SIPROTEC 4 7SJ62 (All versions), SIPROTEC 4 7SJ63 (All versions), SIPROTEC 4 7SJ64 (All versions), SIPROTEC 4 7SJ66 (All versions), SIPROTEC 4 7SS52 (All versions), SIPROTEC 4 7ST6 (All versions), SIPROTEC 4 7UM61 (All versions), SIPROTEC 4 7UM62 (All versions), SIPROTEC 4 7UT612 (All versions), SIPROTEC 4 7UT613 (All versions), SIPROTEC 4 7UT63 (All versions), SIPROTEC 4 7VE6 (All versions), SIPROTEC 4 7VK61 (All versions), SIPROTEC 4 7VU683 (All versions), SIPROTEC 4 Compact 7RW80 (All versions), SIPROTEC 4 Compact 7SD80 (All versions), SIPROTEC 4 Compact 7SJ80 (All versions), SIPROTEC 4 Compact 7SJ81 (All versions), SIPROTEC 4 Compact 7SK80 (All versions), SIPROTEC 4 Compact 7SK81 (All versions). Affected devices do not properly handle interrupted operations of file transfer. This could allow an unauthenticated remote attacker to cause a denial of service condition. To restore normal operations, the devices need to be restarted.","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":"Denial of service in SIPROTEC 4 6MD61","id":"CVE-2024-52504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"matrix-appservice-irc allows IRC Command injection in provisioning API","id":"CVE-2024-52505"},"packages":[],"prev":{"headline":"WordPress Tailored Tools plugin \u003c= 1.8.4 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-52503"},"products":["SIPROTEC 4 6MD61","SIPROTEC 4 6MD63","SIPROTEC 4 6MD66","SIPROTEC 4 6MD665","SIPROTEC 4 7SA522","SIPROTEC 4 7SA6","SIPROTEC 4 7SD5","SIPROTEC 4 7SD610","SIPROTEC 4 7SJ61","SIPROTEC 4 7SJ62","SIPROTEC 4 7SJ63","SIPROTEC 4 7SJ64","SIPROTEC 4 7SJ66","SIPROTEC 4 7SS52","SIPROTEC 4 7ST6","SIPROTEC 4 7UM61","SIPROTEC 4 7UM62","SIPROTEC 4 7UT612","SIPROTEC 4 7UT613","SIPROTEC 4 7UT63","SIPROTEC 4 7VE6","SIPROTEC 4 7VK61","SIPROTEC 4 7VU683","SIPROTEC 4 Compact 7RW80","SIPROTEC 4 Compact 7SD80","SIPROTEC 4 Compact 7SJ80","SIPROTEC 4 Compact 7SJ81","SIPROTEC 4 Compact 7SK80","SIPROTEC 4 Compact 7SK81"],"published":"2025-08-12","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-12","vendors":["Siemens"]},"summary":"Unauthenticated remote attackers can cause a denial of service on Siemens SIPROTEC devices by interrupting file transfers, requiring a device restart to recover.","url":"https://insights.sbomify.com/CVE-2024-52504/"}