CVE-2024-43380: fugit parse and parse_nat stall on lengthy input
Impact The fugit "natural" parser, that turns "every wednesday at 5pm" into "0 17 3", accepted any length of input and went on attempting to parse it, not returning promptly, as expected. The parse call could hold the thread with no end in sight. Fugit dependents that do not check (user) input length for plausability are impacted.
Published Aug 19, 2024 · Updated Aug 21, 2024
Affected packages
fugit
- Ecosystem
- RubyGems
- Affected
- < 1.11.1
- Fixed in
- 1.11.1
- Check
bundle info fugit
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The fugit "natural" parser, that turns "every wednesday at 5pm" into "0 17 * * 3", accepted any length of input and went on attempting to parse it, not returning promptly, as expected. The parse call could hold the thread with no end in sight.
Fugit dependents that do not check (user) input length for plausability are impacted.
Patches
Problem was reported in #104 and the fix was released in fugit 1.11.1
Workarounds
By making sure that Fugit.parse(s), Fugit.do_parse(s), Fugit.parse_nat(s), Fugit.do_parse_nat(s), Fugit::Nat.parse(s), and Fugit::Nat.do_parse(s) are not fed strings too long. 1000 chars feels ok, while 10_000 chars makes it stall.
In fewer words, making sure those fugit methods are not fed unvetted input strings.
References
gh-104
Credited to personnumber3377, bensheldon.
References
- https://github.com/floraison/fugit/security/advisories/GHSA-2m96-52r3-2f3g
- https://nvd.nist.gov/vuln/detail/CVE-2024-43380
- https://github.com/floraison/fugit/issues/104
- https://github.com/floraison/fugit/commit/ad2c1c9c737213d585fff0b51c927d178b2c05a5
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/fugit/CVE-2024-43380.yml
- https://github.com/advisories/GHSA-2m96-52r3-2f3g
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
