{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-1171 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1171 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1171 is a high-severity memory corruption vulnerability in Oracle Solaris, published on 19 Mar 2018. 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-2018-1171 and fix it if it is affected.\n\nWhat it is: CVE-2018-1171 is a high-severity memory corruption vulnerability in Oracle Solaris, published on 19 Mar 2018. 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-2018-1171 in the wild and no public exploit code.\n\nAffected product: Oracle Solaris. 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-2018-1171/ (Markdown: https://insights.sbomify.com/CVE-2018-1171/index.md)","id":"CVE-2018-1171","markdown":"https://insights.sbomify.com/CVE-2018-1171/index.md","name":"CVE-2018-1171","record":{"aliases":["GHSA-22m5-wfj3-68rw"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SmartOS","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges and execute code via a buffer overflow in DTrace DOF file handling on SmartOS.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"smartos","vendor":"joyent"},{"product":"solaris","vendor":"oracle"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"This vulnerability allows local attackers to escalate privileges on vulnerable installations of Joyent SmartOS release-20170803-20170803T064301Z. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the DTrace DOF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code under the context of the host OS. Was ZDI-CAN-5106.","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 Joyent SmartOS","id":"CVE-2018-1171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:solaris","products":["oracle:solaris"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":5,"next":{"headline":"Null dereference in The Squid Software Foundation Squid","id":"CVE-2018-1172"},"packages":[],"prev":{"headline":"Security feature bypass in Volkswagen Customer-Link App","id":"CVE-2018-1170"},"products":["Joyent SmartOS"],"published":"2018-03-19","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.8,"headline":"Integer overflow in SmartOS","id":"CVE-2016-9031","kev_date_added":null,"published":"2016-12-14"},{"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-05","vendors":["Joyent"]},"summary":"Local attackers can escalate privileges and execute code via a buffer overflow in DTrace DOF file handling on SmartOS.","url":"https://insights.sbomify.com/CVE-2018-1171/"}