Secuno
ENNL
Book demo

CVE-2023-41313

Apache Doris vulnerability

9.8 CRITICALEPSS 1.05%
  1. Published12 Mar 2024

Description

The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended to upgrade to version 2.0.0 + or 1.2.8, which fixes this issue.

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

Apache Doris< 1.2.8

Remediation

Fixed in
Apache Doris≥ 1.2.8

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-779879.8
A server-side request forgery (SSRF) vulnerability was identified in the notebook…
CVE-2026-163158.7
OMICRON StationGuard before version 4.10 contains a cryptographic timing side-channel…
CVE-2026-477848.1
In memcached before 1.6.42, password data for SASL password database authentication has…
CVE-2026-477838.1
In memcached before 1.6.42, username data for SASL password database authentication has…
CVE-2026-426028.1
azureauthextension is the Azure Authenticator Extension. From 0.124.0 to 0.150.0, a…
CVE-2026-415889.0
RELATE is a web-based courseware package. Prior to commit 2f68e16, there is a timing…

Frequently asked

Is CVE-2023-41313 being actively exploited?

CVE-2023-41313 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.05%.

How severe is CVE-2023-41313?

CVE-2023-41313 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.05% probability of exploitation.

Which products are affected by CVE-2023-41313?

Affected products include Apache Doris.

How do I fix CVE-2023-41313?

Upgrade affected software to a fixed version, for example Apache Doris 1.2.8 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-41313 against the real software inventory on every managed device, every day. 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.