{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41308 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41308 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41308 is a high-severity memory corruption vulnerability in Subassembly Composer, published on 14 Oct 2022. 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-2022-41308 and fix it if it is affected.\n\nWhat it is: CVE-2022-41308 is a high-severity memory corruption vulnerability in Subassembly Composer, published on 14 Oct 2022. 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-2022-41308 in the wild and no public exploit code.\n\nAffected product: Subassembly Composer. 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-2022-41308/ (Markdown: https://insights.sbomify.com/CVE-2022-41308/index.md)","id":"CVE-2022-41308","markdown":"https://insights.sbomify.com/CVE-2022-41308/index.md","name":"CVE-2022-41308","record":{"aliases":["GHSA-r59r-2m96-gm5j"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Subassembly Composer","requires_auth":"low_privilege","summary":"A malicious PKT file can cause memory corruption in Subassembly Composer, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"autodesk","cpe":[{"product":"subassembly_composer","vendor":"autodesk"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/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":"A maliciously crafted PKT file when consumed through SubassemblyComposer.exe application could lead to memory corruption vulnerability by read access violation. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.","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 Subassembly Composer","id":"CVE-2022-41308","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Autodesk Design Review","id":"CVE-2022-41309"},"packages":[],"prev":{"headline":"Memory corruption in Subassembly Composer","id":"CVE-2022-41307"},"products":["Subassembly Composer"],"published":"2022-10-14","related":[{"cvss_score":7.8,"headline":"Memory corruption in Subassembly Composer","id":"CVE-2022-41305","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":7.8,"headline":"Memory corruption in Subassembly Composer","id":"CVE-2022-41307","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":7.8,"headline":"Memory corruption in Subassembly Composer","id":"CVE-2022-41301","kev_date_added":null,"published":"2022-10-03"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-14","vendors":["n/a"]},"summary":"A malicious PKT file can cause memory corruption in Subassembly Composer, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2022-41308/"}