boa-dev boa up to 0.18.x AsyncGenerator std::panic::catch_unwind uncaught exception

Summaryinfo

A vulnerability was found in boa-dev boa up to 0.18.x. It has been declared as critical. Affected is the function std::panic::catch_unwind of the component AsyncGenerator Handler. The manipulation results in uncaught exception. This vulnerability is reported as CVE-2024-43367. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in boa-dev boa up to 0.18.x. It has been classified as critical. Affected is the function std::panic::catch_unwind of the component AsyncGenerator Handler. The manipulation with an unknown input leads to a uncaught exception vulnerability. CWE is classifying the issue as CWE-248. An exception is thrown from a function, but it is not caught. This is going to have an impact on availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-43367 since 08/09/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.

Upgrading to version 0.19.0 eliminates this vulnerability. Applying the patch 69ea2f52ed976934bff588d6b566bae01be313f7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• boa-dev

Name

• boa

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18

License

• open-source

Website

• Product: https://github.com/boa-dev/boa/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion