{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-53319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-53319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-53319 is a high-severity memory corruption vulnerability in n/a, published on 31 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-53319 and fix it if it is affected.\n\nWhat it is: CVE-2024-53319 is a high-severity memory corruption vulnerability in n/a, published on 31 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-53319 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-53319/ (Markdown: https://insights.sbomify.com/CVE-2024-53319/index.md)","id":"CVE-2024-53319","markdown":"https://insights.sbomify.com/CVE-2024-53319/index.md","name":"CVE-2024-53319","record":{"aliases":["GHSA-9q2w-92gx-fxvp"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualisys C++ SDK","requires_auth":"none","summary":"A heap buffer overflow in the Qualisys C++ SDK allows attackers to cause a Denial of Service via XML text escaping.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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-120","name":"Buffer Copy without Checking Size of Input"}],"description":"A heap buffer overflow in the XML Text Escaping component of Qualisys C++ SDK commit a32a21a allows attackers to cause Denial of Service (DoS) via escaping special XML characters.","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-53319","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":"Memory corruption in n/a","id":"CVE-2024-53320"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-53311"},"products":["n/a"],"published":"2025-01-31","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-02-03","vendors":["n/a"]},"summary":"A heap buffer overflow in the Qualisys C++ SDK allows attackers to cause a Denial of Service via XML text escaping.","url":"https://insights.sbomify.com/CVE-2024-53319/"}