toml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()

[ Description ]Official description

toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() passes unbounded hexadecimal, octal, binary, and decimal digit sequences from lib/parser.js to BigInt() before reduceInteger() in lib/compiler.js checks whether the resulting value fits the TOML 64-bit integer range. Converting a sufficiently long integer string consumes super-linear CPU time and synchronously blocks the Node.js event loop, allowing one attacker-supplied TOML document to deny service to concurrent work in the process. The later range check cannot prevent the conversion cost because it executes after BigInt(). This issue is fixed in version 5.0.1.

[ Fixes ]Fixes and patches

• toml 5.0.1Fixed version · GitHub Advisories · npm package toml: upgrade to 5.0.1 or later (affected <= 5.0.0)

[ Packages ]Affected open-source packages

• toml npmAffected <= 5.0.0 · fixed in 5.0.1 · GHSA-9qmh-m7c6-f92p

[ References ]References

• github.com/BinaryMuse/toml-node/commit/9d52e384f6030932174d1afb0d910154dd62dead
• github.com/BinaryMuse/toml-node/releases/tag/v5.0.1
• github.com/BinaryMuse/toml-node/security/advisories/GHSA-9qmh-m7c6-f92p