Secuno
ENNL
Book demo

CVE-2023-51717

Dataiku Data Science Studio authentication bypass

9.8 CRITICALEPSS 0.61%
  1. Published9 Jan 2024

Description

Dataiku DSS before 11.4.5 and 12.4.1 has Incorrect Access Control that could lead to a full authentication bypass.

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

Dataiku Data Science Studio≥ 12.0.0 < 12.4.1 · < 11.4.5

Remediation

Fixed in
Dataiku Data Science Studio≥ 12.4.1

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-843138.8
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, POST…
CVE-2026-1093728.7
ZITADEL 4.x before 4.19.2 and 3.x through 3.4.15 contains an authentication bypass in…
CVE-2026-1093138.1
Grav Login plugin 2.7.0 before 3.9.9 contains an authentication bypass vulnerability…
CVE-2026-1093128.1
Grav Login plugin 2.7.0 before 3.9.9 contains an authentication bypass in…
CVE-2026-10890710.0
A vulnerability was determined in Netcore NR268 1.7.121109. Affected is the function…
CVE-2026-1088658.2
AmoyLab Unla through 0.10.0 contains an authentication bypass vulnerability that allows…

Frequently asked

Is CVE-2023-51717 being actively exploited?

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

How severe is CVE-2023-51717?

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

Which products are affected by CVE-2023-51717?

Affected products include Dataiku Data Science Studio.

How do I fix CVE-2023-51717?

Upgrade affected software to a fixed version, for example Dataiku Data Science Studio 12.4.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-51717 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.