Vulnerability in fugit (CVE-2024-43380)
Summary
Vulnerability in fugit (CVE-2024-43380). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.11.1 or later.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-43380 has been found in fugit.
Risk of unauthorized operations or information disclosure.
What to do: upgrade fugit to 1.11.1 or later.
If unsure, ask your IT team or search "fugit CVE-2024-43380" on the vendor's site.
CVE-2024-43380 (fugit) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.11.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in fugit.
Check the vendor advisory for the affected versions of fugit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.11.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'fugit' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'fugit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
fugitを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade fugit to 1.11.1ステージング環境で 1.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2024-43380 ruby-fugit
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com