{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-50953 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-50953 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-50953 is a high-severity denial of service vulnerability in n/a, published on 15 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-50953 and fix it if it is affected.\n\nWhat it is: CVE-2024-50953 is a high-severity denial of service vulnerability in n/a, published on 15 Jan 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-50953 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-2024-50953/ (Markdown: https://insights.sbomify.com/CVE-2024-50953/index.md)","id":"CVE-2024-50953","markdown":"https://insights.sbomify.com/CVE-2024-50953/index.md","name":"CVE-2024-50953","record":{"aliases":["GHSA-4vwx-53cp-qmh4"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"XINJE PLC","requires_auth":"none","summary":"Attackers can cause a Denial of Service on XINJE XL5E-16T PLCs by sending crafted Modbus messages.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"An issue in XINJE XL5E-16T V3.7.2a allows attackers to cause a Denial of Service (DoS) via a crafted Modbus message.","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 n/a","id":"CVE-2024-50953","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":"Denial of service in n/a","id":"CVE-2024-50954"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2024-50948"},"products":["n/a"],"published":"2025-01-15","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-03-24","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service on XINJE XL5E-16T PLCs by sending crafted Modbus messages.","url":"https://insights.sbomify.com/CVE-2024-50953/"}