Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 22 November 2024.
- Which products and versions are affected?
- smol-toml (npm) SEMVER:introduced=0,fixed=1.3.1.
- Is there a fix for This vulnerability?
- Yes. smol-toml (npm): upgrade to 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run smol-toml (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- smol-toml (npm): upgrade to 1.3.1 or later
npm install smol-toml@1.3.1
Technical details
The vulnerability is an uncontrolled recursion issue (CWE-674) in the TOML parser. When parsing or stringifying deeply nested inline table structures, the library does not limit recursion depth, leading to a stack overflow that terminates the process. The attack is network-accessible and requires no authentication or user interaction—an attacker can send the malicious TOML directly to any application that parses arbitrary TOML input. The parser will crash if the application does not catch exceptions. Version 1.3.1 introduces a depth limit (default 1000) to make the behavior controlled and documented; earlier versions are affected.
Affected products
- squirrelchat smol-toml <= 1.3.0
Timeline
- 2024-11-22: disclosed
- 2024-11-18: patched: Version 1.3.1 released with depth limit enforcement