{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-25724 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-25724 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25724 is a high-severity memory corruption vulnerability in n/a, published on 21 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-25724 and fix it if it is affected.\n\nWhat it is: CVE-2024-25724 is a high-severity memory corruption vulnerability in n/a, published on 21 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-25724 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-25724/ (Markdown: https://insights.sbomify.com/CVE-2024-25724/index.md)","id":"CVE-2024-25724","markdown":"https://insights.sbomify.com/CVE-2024-25724/index.md","name":"CVE-2024-25724","record":{"aliases":["GHSA-29gq-rw72-mrqg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RTI Connext Professional","requires_auth":"low_privilege","summary":"Attackers can execute code or crash RTI Connext services via malicious XML input in Routing, Recording, Queuing, or Cloud Discovery services.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"connext_professional","vendor":"rti"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:H/C:L/I:H/PR:L/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"In RTI Connext Professional 5.3.1 through 6.1.0 before 6.1.1, a buffer overflow in XML parsing from Routing Service, Recording Service, Queuing Service, and Cloud Discovery Service allows attackers to execute code with the affected service's privileges, compromise the service's integrity, leak sensitive information, or crash the service. These attacks could be done via a remote malicious RTPS message; a compromised call with malicious parameters to the RTI_RoutingService_new, rti::recording::Service, RTI_QueuingService_new, or RTI_CDS_Service_new public APIs; or a compromised local file system containing a malicious XML file.","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":"Memory corruption in n/a","id":"CVE-2024-25724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2024-25728"},"packages":[],"prev":{"headline":"ZenML Server Remote Privilege Escalation Vulnerability","id":"CVE-2024-25723"},"products":["n/a"],"published":"2024-05-21","related":[{"cvss_score":9.2,"headline":"Memory corruption in Connext Professional","id":"CVE-2026-2467","kev_date_added":null,"published":"2026-06-17"},{"cvss_score":9.2,"headline":"Out-of-bounds Read vulnerability in RTI Connext Professional (Core Libraries) allows Overread Buffers.","id":"CVE-2026-3894","kev_date_added":null,"published":"2026-06-17"},{"cvss_score":9.1,"headline":"SQL injection in Connext Professional","id":"CVE-2024-52057","kev_date_added":null,"published":"2024-12-13"},{"cvss_score":8.8,"headline":"Memory corruption in Connext Professional","id":"CVE-2026-7300","kev_date_added":null,"published":"2026-06-17"},{"cvss_score":8.8,"headline":"XML external entity in Connext Professional","id":"CVE-2025-14543","kev_date_added":null,"published":"2026-04-30"},{"cvss_score":8.8,"headline":"XML external entity in Connext Professional","id":"CVE-2026-4374","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":8.6,"headline":"Potential arbitrary command execution in System Designer while parsing malicious HTTP/REST requests","id":"CVE-2024-52058","kev_date_added":null,"published":"2024-12-13"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-27","vendors":["n/a"]},"summary":"Attackers can execute code or crash RTI Connext services via malicious XML input in Routing, Recording, Queuing, or Cloud Discovery services.","url":"https://insights.sbomify.com/CVE-2024-25724/"}