{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-4291 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-4291 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-4291 is a high-severity vulnerability in Hancom Office, published on 6 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-4291 and fix it if it is affected.\n\nWhat it is: CVE-2016-4291 is a high-severity vulnerability in Hancom Office, published on 6 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-4291 in the wild and no public exploit code.\n\nAffected product: Hancom Office. 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-2016-4291/ (Markdown: https://insights.sbomify.com/CVE-2016-4291/index.md)","id":"CVE-2016-4291","markdown":"https://insights.sbomify.com/CVE-2016-4291/index.md","name":"CVE-2016-4291","record":{"aliases":["GHSA-crxv-hwq9-wj7h"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Hancom Office","requires_auth":"none","summary":"An integer overflow in Hancom Office allows remote code execution via a malicious HShow document due to insufficient bounds checking during memory allocation.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"hancom_office_2014","vendor":"hancom"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"When opening a Hangul HShow Document (.hpt) and processing a structure within the document, Hancom Office 2014 will use a field from the structure in an operation that can cause the integer to overflow. This result is then used to allocate memory to copy file data in. Due to the lack of bounds checking on the integer, the allocated memory buffer can be made to be undersized at which point the reading of file data will write outside the bounds of the buffer. This can lead to code execution under the context of the application.","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":"Integer overflow in Hancom Office","id":"CVE-2016-4291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Hancom Office","id":"CVE-2016-4292"},"packages":[],"prev":{"headline":"Integer overflow in Hancom Office","id":"CVE-2016-4290"},"products":["Hancom Office"],"published":"2017-01-06","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2016-4293","kev_date_added":null,"published":"2017-04-20"},{"cvss_score":7.8,"headline":"Integer overflow in Hancom Office","id":"CVE-2016-4290","kev_date_added":null,"published":"2017-01-06"},{"cvss_score":7.8,"headline":"Memory corruption in Hancom Office","id":"CVE-2016-4292","kev_date_added":null,"published":"2017-01-06"},{"cvss_score":7.8,"headline":"Memory corruption in Hancom Office","id":"CVE-2016-4294","kev_date_added":null,"published":"2017-01-06"},{"cvss_score":7.8,"headline":"Memory corruption in Hancom Office","id":"CVE-2016-4295","kev_date_added":null,"published":"2017-01-06"},{"cvss_score":7.8,"headline":"Memory corruption in Hancom Office","id":"CVE-2016-4296","kev_date_added":null,"published":"2017-01-06"}],"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-06","vendors":["Hancom"]},"summary":"An integer overflow in Hancom Office allows remote code execution via a malicious HShow document due to insufficient bounds checking during memory allocation.","url":"https://insights.sbomify.com/CVE-2016-4291/"}