Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

RubyGems package

fugit

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3RubyGemsPublished

    fugit parse and parse_nat stall on lengthy input

    CVE-2024-43380 · GHSA-2m96-52r3-2f3g

    Affected
    • RubyGems fugit < 1.11.1
    Fixed in
    1.11.1· Vendor fix available
    Issue
    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.doparse(s), Fugit.parsenat(s), Fugit.doparsenat(s), Fugit::Nat.parse(s), and Fugit::Nat.doparse(s) are not fed strings too long. 1000 chars feels ok, while 10000 chars makes it stall. In fewer words, making sure those fugit methods are not fed unvetted input strings. References gh-104

    Recommended action: Upgrade to 1.11.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →