{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9031 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-9031 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-9031 is a high-severity vulnerability in Joyent SmartOS, published on 14 Dec 2016. 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-2016-9031 and fix it if it is affected.\n\nWhat it is: CVE-2016-9031 is a high-severity vulnerability in Joyent SmartOS, published on 14 Dec 2016. 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-2016-9031 in the wild and no public exploit code.\n\nAffected product: Joyent SmartOS. 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-9031/ (Markdown: https://insights.sbomify.com/CVE-2016-9031/index.md)","id":"CVE-2016-9031","markdown":"https://insights.sbomify.com/CVE-2016-9031/index.md","name":"CVE-2016-9031","record":{"aliases":["GHSA-9vxv-mj8f-wqwx"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SmartOS kernel","requires_auth":"low_privilege","summary":"An integer overflow in the Hyprlofs file system allows attackers to cause a kernel panic and potentially escalate privileges on SmartOS.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"smartos","vendor":"joyent"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"An exploitable integer overflow exists in the Joyent SmartOS 20161110T013148Z Hyprlofs file system. The vulnerability is present in the Ioctl system call with the command HYPRLOFS_ADD_ENTRIES when dealing with 32-bit file systems. An attacker can craft an input that can cause a kernel panic and potentially be leveraged into a full privilege escalation vulnerability. This vulnerability is distinct from CVE-2016-8733.","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 SmartOS","id":"CVE-2016-9031","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 SmartOS","id":"CVE-2016-9032"},"packages":[],"prev":{"headline":"Open redirect in n/a","id":"CVE-2016-9028"},"products":["SmartOS"],"published":"2016-12-14","related":[{"cvss_score":7.8,"headline":"Use after free in Joyent SmartOS","id":"CVE-2018-1166","kev_date_added":null,"published":"2018-02-21"},{"cvss_score":7.8,"headline":"Integer overflow in SmartOS","id":"CVE-2016-8733","kev_date_added":null,"published":"2016-12-14"},{"cvss_score":7,"headline":"Memory corruption in Joyent SmartOS","id":"CVE-2018-1171","kev_date_added":null,"published":"2018-03-19"},{"cvss_score":7,"headline":"Memory corruption in Joyent SmartOS","id":"CVE-2018-1165","kev_date_added":null,"published":"2018-02-21"},{"cvss_score":7,"headline":"Memory corruption in SmartOS","id":"CVE-2016-9032","kev_date_added":null,"published":"2016-12-14"},{"cvss_score":7,"headline":"Memory corruption in SmartOS","id":"CVE-2016-9033","kev_date_added":null,"published":"2016-12-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["Joyent"]},"summary":"An integer overflow in the Hyprlofs file system allows attackers to cause a kernel panic and potentially escalate privileges on SmartOS.","url":"https://insights.sbomify.com/CVE-2016-9031/"}