{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-40770 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-40770 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-40770 is a high-severity memory corruption vulnerability in Adobe Prelude, published on 22 Nov 2021. 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-2021-40770 and fix it if it is affected.\n\nWhat it is: CVE-2021-40770 is a high-severity memory corruption vulnerability in Adobe Prelude, published on 22 Nov 2021. 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-2021-40770 in the wild and no public exploit code.\n\nAffected product: Adobe Prelude. 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-2021-40770/ (Markdown: https://insights.sbomify.com/CVE-2021-40770/index.md)","id":"CVE-2021-40770","markdown":"https://insights.sbomify.com/CVE-2021-40770/index.md","name":"CVE-2021-40770","record":{"aliases":["GHSA-pmmm-mgxp-rwv5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Adobe Prelude","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening a malicious M4A file in Adobe Prelude.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"adobe","cpe":[{"product":"prelude","vendor":"adobe"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"},{"id":"CWE-788","name":"Access of Memory Location After End of Buffer"}],"description":"Adobe Prelude version 10.1 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious M4A file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required in that the victim must open a specially crafted file to exploit this vulnerability.","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":"Adobe Prelude M4A File Parsing Memory Corruption Arbitrary Code Execution","id":"CVE-2021-40770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Adobe Prelude WAV File Parsing Memory Corruption Arbitrary Code Execution","id":"CVE-2021-40771"},"packages":[],"prev":{"headline":"Adobe Character Animator SVG File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability","id":"CVE-2021-40769"},"products":["Prelude"],"published":"2021-11-22","related":[{"cvss_score":8.8,"headline":"Memory corruption in Adobe Prelude","id":"CVE-2020-9677","kev_date_added":null,"published":"2020-07-22"},{"cvss_score":8.8,"headline":"Memory corruption in Adobe Prelude","id":"CVE-2020-9678","kev_date_added":null,"published":"2020-07-22"},{"cvss_score":8.8,"headline":"Memory corruption in Adobe Prelude","id":"CVE-2020-9680","kev_date_added":null,"published":"2020-07-22"},{"cvss_score":7.8,"headline":"Adobe Prelude Corruption could lead to Arbitrary code execution","id":"CVE-2021-43754","kev_date_added":null,"published":"2022-06-15"},{"cvss_score":7.8,"headline":"Adobe Prelude WAV File Parsing Memory Corruption Arbitrary Code Execution","id":"CVE-2021-40771","kev_date_added":null,"published":"2021-11-22"},{"cvss_score":7.8,"headline":"Adobe Prelude M4A File Parsing Memory Corruption Arbitrary Code Execution","id":"CVE-2021-40772","kev_date_added":null,"published":"2021-11-22"}],"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-04-23","vendors":["Adobe"]},"summary":"Attackers can execute arbitrary code by tricking users into opening a malicious M4A file in Adobe Prelude.","url":"https://insights.sbomify.com/CVE-2021-40770/"}