{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2910 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2910 is a high-severity memory corruption vulnerability in libxls, published on 2 Dec 2020. 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-2017-2910 and fix it if it is affected.\n\nWhat it is: CVE-2017-2910 is a high-severity memory corruption vulnerability in libxls, published on 2 Dec 2020. 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-2017-2910 in the wild and no public exploit code.\n\nAffected product: libxls. 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-2017-2910/ (Markdown: https://insights.sbomify.com/CVE-2017-2910/index.md)","id":"CVE-2017-2910","markdown":"https://insights.sbomify.com/CVE-2017-2910/index.md","name":"CVE-2017-2910","record":{"aliases":["GHSA-p854-92x2-rx7x","UBUNTU-CVE-2017-2910"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"libxls library","requires_auth":"none","summary":"A specially crafted XLS file can trigger an out-of-bounds write in libxls, leading to remote code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"libxls","vendor":"libxls_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An exploitable Out-of-bounds Write vulnerability exists in the xls_addCell function of libxls 2.0. A specially crafted xls file can cause a memory corruption resulting in remote code execution. An attacker can send malicious xls file to trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in libxls","id":"CVE-2017-2910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Circle","id":"CVE-2017-2911"},"packages":[],"prev":{"headline":"Denial of service in Mongoose","id":"CVE-2017-2909"},"products":["libxls"],"published":"2020-12-02","related":[{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2018-20452","kev_date_added":null,"published":"2018-12-25"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12108","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12109","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12110","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-12111","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-2897","kev_date_added":null,"published":"2017-11-20"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A specially crafted XLS file can trigger an out-of-bounds write in libxls, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2017-2910/"}