CVE-2023-51717
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDataiku DSS before 11.4.5 and 12.4.1 has Incorrect Access Control that could lead to a full authentication bypass.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDataiku DSS versions prior to 11.4.5 and 12.4.1 contain an incorrect access control vulnerability that allows full authentication bypass. An unauthenticated attacker could potentially gain complete access to the Dataiku DSS platform by exploiting this flaw.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 11.4.5>= 12.0.0, < 12.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Dataiku DSS installed versionLog into the Dataiku DSS web interface and check the version number displayed in the footer of any page, or run 'dss version' from the command line on the DSS host server.Affected if The installed version is lower than 11.4.5 OR falls between 12.0.0 and 12.4.0 (inclusive).
-
Confirm version is within vulnerable rangeCompare your identified version against the affected ranges: any version < 11.4.5, or any version from 12.0.0 up to but not including 12.4.1.Affected if Your version matches either of these ranges: versions 12.0.0 through 12.4.0, or any version below 11.4.5.
-
Verify DSS is network-accessibleConfirm that the Dataiku DSS web interface is reachable over the network (by default on port 11000). The authentication bypass can be exploited by any unauthenticated network attacker.Affected if DSS is exposed to untrusted network access and the version is within the vulnerable ranges identified above.
You are affected if your Dataiku DSS version is below 11.4.5 or between 12.0.0 and 12.4.0 inclusive, and the interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped11.4.512.4.1
Upgrade Dataiku DSS to version 11.4.5, 12.4.1, or later to resolve the incorrect access control vulnerability. If immediate upgrading is not possible, restrict network access to the DSS interface as a temporary compensating control.
11.4.5 or 12.4.1 (and later versions in respective branches)
- Backup the Dataiku DSS instance, including all projects, configurations, and databases
- Stop the Dataiku DSS service
- Review the Dataiku upgrade documentation for the target version (11.4.5 or 12.4.1) for any specific migration requirements
- Download the appropriate installer for the fixed version (11.4.5 for 11.x branch or 12.4.1+ for 12.x branch) from the official Dataiku download page
- Run the installer or follow the upgrade procedure for your deployment method (Docker, installer, etc.)
- Verify that the upgrade completed successfully by checking the version in the UI or via command line
- Start the Dataiku DSS service
- Test that authentication is working correctly and verify the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data