CVE-2020-8817
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 6.0.5 allows attackers write access to the project to modify the "Created by" metadata.
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 6.0.5 contain an access control flaw where authenticated users with write permissions to a project can modify the 'Created by' metadata field, allowing impersonation or false attribution of project authorship.
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< 6.0.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
-
Determine installed Dataiku DSS versionLocate the version file or use the dss CLI command (dss version) to identify the currently installed Dataiku DSS versionAffected if The installed version is prior to 6.0.5 (e.g., 6.0.4, 6.0.3, etc.)
-
Identify user project permissionsReview user access controls within Dataiku DSS admin interface or via the projects list API to determine which users have write permissions on projectsAffected if Any authenticated user has write permissions to one or more projects (not restricted to admin-only)
-
Verify metadata field edit capabilityUsing an authenticated user with write permissions, attempt to modify the 'Created by' field in a project's metadata settings (typically found in Project > Settings > Metadata)Affected if The 'Created by' field is editable and can be changed to another user account
-
Check audit logs for metadata modificationsReview Dataiku DSS audit logs for recent changes to project metadata, specifically looking for 'Created by' field modificationsAffected if Recent modifications to the 'Created by' field exist and were performed by non-admin users
You are affected if Dataiku DSS version is below 6.0.5 AND users with write permissions exist in your environment, allowing unauthorized modification of project authorship metadata.
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.
From vendor data6.0.5
Upgrade to Dataiku DSS version 6.0.5 or later. Until then, restrict write access to trusted personnel only and monitor audit logs for unexpected metadata changes.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8817 — 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-2020-8817 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