{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-23617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-23617 is a critical memory corruption vulnerability in Symantec Data Loss Prevention, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-23617 and fix it if it is affected.\n\nWhat it is: CVE-2024-23617 is a critical memory corruption vulnerability in Symantec Data Loss Prevention, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-23617 in the wild and no public exploit code.\n\nAffected product: Symantec Data Loss Prevention. 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-23617/ (Markdown: https://insights.sbomify.com/CVE-2024-23617/index.md)","id":"CVE-2024-23617","markdown":"https://insights.sbomify.com/CVE-2024-23617/index.md","name":"CVE-2024-23617","record":{"aliases":["GHSA-c2h4-p5j3-jcgh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Symantec Data Loss Prevention","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening crafted documents in Symantec Data Loss Prevention.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XI","cpe":[{"product":"symantec_data_center_security_server","vendor":"broadcom"}],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A buffer overflow vulnerability exists in Symantec Data Loss Prevention version 14.0.2 and before. A remote, unauthenticated attacker can exploit this vulnerability by enticing a user to open a crafted document to achieve code execution.","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":"Symantec Data Loss Prevention Buffer Overflow","id":"CVE-2024-23617","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":"Arris SURFboard SBG6950AC2 Arbitrary Code Execution Vulnerability","id":"CVE-2024-23618"},"packages":[],"prev":{"headline":"Symantec Server Management Suite Buffer Overflow","id":"CVE-2024-23616"},"products":["Data Loss Prevention"],"published":"2024-01-25","related":[{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2016-5309","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2016-5310","kev_date_added":null,"published":"2017-04-14"}],"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":"2024-10-18","vendors":["Symantec"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening crafted documents in Symantec Data Loss Prevention.","url":"https://insights.sbomify.com/CVE-2024-23617/"}