fugit parse and parse_nat stall on lengthy input

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-43380: 0.80% estimated exploitation activity in the next 30 days; percentile 56.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

19 Aug 2024, 17:29 UTC

Last modified by the source

21 Aug 2024, 14:55 UTC

Source last checked

26 Oct 2026, 15:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2m96-52r3-2f3g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-43380

Advisory: fugit parse and parse_nat stall on lengthy input
IDs: CVE-2024-43380, GHSA-2m96-52r3-2f3g
Record: https://patchnext.com/advisories/cve-2024-43380 (revision 1, source checked 26 Oct 2026, 15:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: fugit 1.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems fugit: affected < 1.11.1; fixed in 1.11.1

## Suggested inspection (read-only)
- RubyGems fugit: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on fugit.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2m96-52r3-2f3g (GitHub-reviewed advisory GHSA-2m96-52r3-2f3g lists affected ranges: RubyGems fugit >=0 <1.11.1)

Commands are suggestions: review each one before running it.