{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-43357 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-43357 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-43357 is a high-severity memory corruption vulnerability in tc39 ecma262, published on 15 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-43357 and fix it if it is affected.\n\nWhat it is: CVE-2024-43357 is a high-severity memory corruption vulnerability in tc39 ecma262, published on 15 Aug 2024. 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-2024-43357 in the wild and no public exploit code.\n\nAffected product: tc39 ecma262. 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-2024-43357/ (Markdown: https://insights.sbomify.com/CVE-2024-43357/index.md)","id":"CVE-2024-43357","markdown":"https://insights.sbomify.com/CVE-2024-43357/index.md","name":"CVE-2024-43357","record":{"aliases":[],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript engine","requires_auth":"none","summary":"A specification flaw in async generators allows type confusion and pointer dereference, potentially enabling code execution or crashes in JavaScript engines.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-476","name":"NULL Pointer Dereference"},{"id":"CWE-248","name":"Uncaught Exception"}],"description":"ECMA-262 is the language specification for the scripting language ECMAScript. A problem in the ECMAScript (JavaScript) specification of async generators, introduced by a May 2021 spec refactor, may lead to mis-implementation in a way that could present as a security vulnerability, such as type confusion and pointer dereference.\n\nThe internal async generator machinery calls regular promise resolver functions on IteratorResult (`{ done, value }`) objects that it creates, assuming that the IteratorResult objects will not be then-ables. Unfortunately, these IteratorResult objects inherit from `Object.prototype`, so these IteratorResult objects can be made then-able, triggering arbitrary behaviour, including re-entering the async generator machinery in a way that violates some internal invariants.\n\nThe ECMAScript specification is a living standard and the issue has been addressed at the time of this advisory's public disclosure. JavaScript engine implementors should refer to the latest specification and update their implementations to comply with the `AsyncGenerator` section.\n\n## References\n\n- https://github.com/tc39/ecma262/commit/1e24a286d0a327d08e1154926b3ee79820232727\n- https://bugzilla.mozilla.org/show_bug.cgi?id=1901411\n- https://github.com/boa-dev/boa/security/advisories/GHSA-f67q-wr6w-23jq\n- https://bugs.webkit.org/show_bug.cgi?id=275407\n- https://issues.chromium.org/issues/346692561\n- https://www.cve.org/CVERecord?id=CVE-2024-7652","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"JavaScript specification issue may lead to type confusion and pointer dereference in implementations","id":"CVE-2024-43357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":10,"next":{"headline":"XSS vulnerability in filter view","id":"CVE-2024-43358"},"packages":[],"prev":{"headline":"WordPress oik plugin \u003c= 4.12.0 - Arbitrary File Deletion vulnerability","id":"CVE-2024-43356"},"products":["ecma262"],"published":"2024-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-15","vendors":["tc39"]},"summary":"A specification flaw in async generators allows type confusion and pointer dereference, potentially enabling code execution or crashes in JavaScript engines.","url":"https://insights.sbomify.com/CVE-2024-43357/"}