Advisory

GHSA-2m96-52r3-2f3g

Also known as: CVE-2024-43380

Summary

fugit parse and parse_nat stall on lengthy input

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-08-19 17:29 UTC
Modified
2026-08-07 08:12 UTC

Affected packages and fixes

fugit

RubyGems · All systems

Affected

  • introduced 0, fixed 1.11.1 (ecosystem)

Fixed versions

1.11.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences