CVE-2024-43380
highpriority · track · 30EPSS 0.008 · 56 %ileDEEUUSEPSS · scored 2026-10-27
fugit contains time tools for flor and the floraison group. 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 plausibility are impacted. A fix was released in fugit 1.11.1.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.3–7.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (5)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2024-2159IBM License Metric Tool: Mehrere SchwachstellenDeutsch2024-09-16csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um einen Denial of Service Angriff durchzuführen oder vertrauliche Informationen offenzulegen.
- WID-SEC-W-2025-0741LogStash: Schwachstelle ermöglicht Denial of ServiceDeutsch2025-04-08csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in LogStash ausnutzen, um einen Denial of Service Angriff durchzuführen.
- GHSA-2m96-52r3-2f3gfugit parse and parse_nat stall on lengthy input2024-08-19ghsa · osvUS
### 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](https://rubygems.org/gems/fugit/versions/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
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (11)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2024-43380cnnvd
- https://cxsecurity.com/cveshow/CVE-2024-43380/cnnvd
- https://github.com/floraison/fugit/commit/ad2c1c9c737213d585fff0b51c927d178b2c05a5cnnvd
- https://github.com/floraison/fugit/issues/104cnnvd
- https://github.com/floraison/fugit/security/advisories/GHSA-2m96-52r3-2f3gcnnvd
- https://github.com/floraison/fugit/commit/ad2c1c9c737213d585fff0b51c927d178b2c05a5enisa_euvd
- https://github.com/floraison/fugit/issues/104enisa_euvd
- https://github.com/floraison/fugit/security/advisories/GHSA-2m96-52r3-2f3genisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan