{"answers":{"affected":"2 open source packages ship an affected version, including deno. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32619 in the wild and no public exploit code.","fix":"Upgrade deno to 1.10.2 or later.","what":"CVE-2021-32619 is a critical vulnerability in denoland deno, published on 28 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32619 and fix it if it is affected.\n\nWhat it is: CVE-2021-32619 is a critical vulnerability in denoland deno, published on 28 May 2021. 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-2021-32619 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- deno (crates.io): affected from 1.5.0; fixed in 1.10.2\n- deno (crates.io): affected from 1.5.0; fixed in 1.10.2\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-32619/ (Markdown: https://insights.sbomify.com/CVE-2021-32619/index.md)","id":"CVE-2021-32619","markdown":"https://insights.sbomify.com/CVE-2021-32619/index.md","name":"CVE-2021-32619","record":{"aliases":["GHSA-xpwj-7v8q-mcgj","JLSEC-2026-98"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Deno JavaScript runtime","requires_auth":"none","summary":"Attackers can bypass network and file system permission checks in Deno by using static imports within dynamically imported modules.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"deno","vendor":"deno"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"Deno is a runtime for JavaScript and TypeScript that uses V8 and is built in Rust. In Deno versions 1.5.0 to 1.10.1, modules that are dynamically imported through `import()` or `new Worker` might have been able to bypass network and file system permission checks when statically importing other modules. The vulnerability has been patched in Deno release 1.10.2.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Static imports inside dynamically imported modules do not adhere to permission checks","id":"CVE-2021-32619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Users registered with email verification can self re-activate their disabled accounts","id":"CVE-2021-32620"},"packages":[{"ecosystem":"crates.io","fixed":["1.10.2"],"introduced":["1.5.0"],"last_affected":[],"package":"deno","purl":null,"source":"GHSA-xpwj-7v8q-mcgj"},{"ecosystem":"crates.io","fixed":["1.10.2"],"introduced":["1.5.0"],"last_affected":[],"package":"deno","purl":"pkg:cargo/deno","source":"GHSA-xpwj-7v8q-mcgj"}],"prev":{"headline":"Open Redirect Vulnerability","id":"CVE-2021-32618"},"products":["deno"],"published":"2021-05-28","related":[{"cvss_score":10,"headline":"Deno improperly handles resizable ArrayBuffer","id":"CVE-2023-28445","kev_date_added":null,"published":"2023-03-23"},{"cvss_score":10,"headline":"Sandbox bypass leading to arbitrary code execution in Deno","id":"CVE-2022-24783","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":9.2,"headline":"Deno node:crypto doesn't finalize cipher","id":"CVE-2026-22863","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":8.8,"headline":"Deno interactive permission prompt spoofing via improper ANSI stripping","id":"CVE-2024-27936","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":8.8,"headline":"Deno is vulnerable to interactive `run` permission prompt spoofing via improper ANSI neutralization","id":"CVE-2023-28446","kev_date_added":null,"published":"2023-03-24"},{"cvss_score":8.6,"headline":"Deno missing \"--allow-net\" permission check for built-in Node modules","id":"CVE-2023-33966","kev_date_added":null,"published":"2023-05-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-03","vendors":["denoland"]},"summary":"Attackers can bypass network and file system permission checks in Deno by using static imports within dynamically imported modules.","url":"https://insights.sbomify.com/CVE-2021-32619/"}