Secuno
ENNL
Book demo

CVE-2024-25678

Litespeedtech Lsquic vulnerability

9.8 CRITICALEPSS 0.35%
  1. Published9 Feb 2024

Description

In LiteSpeed QUIC (LSQUIC) Library before 4.0.4, DCID validation is mishandled.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Litespeedtech Lsquic< 4.0.4

Remediation

Fixed in
Litespeedtech Lsquic≥ 4.0.4

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-927019.1
Cocos AI is a confidential computing system for running AI workloads inside trusted…
CVE-2026-768528.8
Netcore NR268 firmware version 1.7.121109 has an improper integrity verification flaw…
CVE-2026-541748.3
melange allows users to build apk packages using declarative pipelines. Apko prior to…
CVE-2026-825498.3
A vulnerability was identified in Linux Foundation Magma 1.9.0. This affects an unknown…
CVE-2026-758039.1
Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can…
CVE-2026-756259.0
Kraken agents fail to verify peer-to-peer downloaded blobs against their requested…

Frequently asked

Is CVE-2024-25678 being actively exploited?

CVE-2024-25678 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.35%.

How severe is CVE-2024-25678?

CVE-2024-25678 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.35% probability of exploitation.

Which products are affected by CVE-2024-25678?

Affected products include Litespeedtech Lsquic.

How do I fix CVE-2024-25678?

Upgrade affected software to a fixed version, for example Litespeedtech Lsquic 4.0.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-25678 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.