{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9305 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-9305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-9305 is a critical use after free vulnerability in n/a, published on 25 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-9305 and fix it if it is affected.\n\nWhat it is: CVE-2016-9305 is a critical use after free vulnerability in n/a, published on 25 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-9305 in the wild and no public exploit code.\n\nAffected product: n/a. 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-9305/ (Markdown: https://insights.sbomify.com/CVE-2016-9305/index.md)","id":"CVE-2016-9305","markdown":"https://insights.sbomify.com/CVE-2016-9305/index.md","name":"CVE-2016-9305","record":{"aliases":["GHSA-f2hc-5rqr-r3c2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Autodesk FBX SDK","requires_auth":"none","summary":"Attackers can exploit improper handling of deleted objects in the Autodesk FBX SDK to access uninitialized pointers, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fbx_software_development_kit","vendor":"autodesk"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-19","name":null}],"description":"Improper handling in the Autodesk FBX-SDK before 2017.1 of type mismatches and previously deleted objects related to reading and converting malformed FBX format files can allow attackers to gain access to uninitialized pointers.","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":"Use after free in n/a","id":"CVE-2016-9305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-9306"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2016-9304"},"products":["n/a"],"published":"2017-01-25","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9303","kev_date_added":null,"published":"2017-01-25"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9306","kev_date_added":null,"published":"2017-01-25"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9307","kev_date_added":null,"published":"2017-01-25"},{"cvss_score":8.8,"headline":"Memory corruption in Autodesk FBX-SDK","id":"CVE-2020-7081","kev_date_added":null,"published":"2020-04-17"},{"cvss_score":8.8,"headline":"Use after free in Autodesk FBX-SDK","id":"CVE-2020-7082","kev_date_added":null,"published":"2020-04-17"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9304","kev_date_added":null,"published":"2017-01-25"}],"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":["n/a"]},"summary":"Attackers can exploit improper handling of deleted objects in the Autodesk FBX SDK to access uninitialized pointers, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2016-9305/"}