All reports
Medium

fugit parse and parse_nat stall on lengthy input

Affected versions

Affected versions
Unknown
Fixed version
Not reported
RubyGemsfugit
Affected versions
< 1.11.1
Fixed version
1.11.1

Exploitation

CVE-2024-43380

Probability of exploitation in the next 30 days: 0.80%

FIRST EPSS · 2026-11-18

Description

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

Links

Credits

  • personnumber3377
  • bensheldon