dataiku vulnerabilities

Products

• data science studio 5

Latest dataiku CVEs

Newest publication first

1. CVE-2023-51717 Dataiku DSS before 11.4.5 and 12.4.1 has Incorrect Access Control that could lead to a full authentication bypass.

   Published 2024-01-09

   Critical·CVSS 9.8

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

2. CVE-2023-24045 In Dataiku DSS 11.2.1, an attacker can download other Dataiku files that were uploaded to the myfiles section by specifying the target username in a download request.

   Published 2023-03-01

   Medium·CVSS 6.5

   In Dataiku DSS 11.2.1, an attacker can download other Dataiku files that were uploaded to the myfiles section by specifying the target username in a download request.

3. CVE-2021-27225 In Dataiku DSS before 8.0.6, insufficient access control in the Jupyter notebooks integration allows users (who have coding permissions) to read and overwrite notebooks in projects that they are not a...

   Published 2021-03-01

   Medium·CVSS 5.4

   In Dataiku DSS before 8.0.6, insufficient access control in the Jupyter notebooks integration allows users (who have coding permissions) to read and overwrite notebooks in projects that they are not authorized to access.

4. CVE-2020-8817 Dataiku DSS before 6.0.5 allows attackers write access to the project to modify the "Created by" metadata.

   Published 2020-09-14

   High·CVSS 8.1

   Dataiku DSS before 6.0.5 allows attackers write access to the project to modify the "Created by" metadata.

5. CVE-2018-10732 The REST API in Dataiku DSS before 4.2.3 allows remote attackers to obtain sensitive information (i.e., determine if a username is valid) because of profile pictures visibility.

   Published 2018-05-28

   Medium·CVSS 5.3

   The REST API in Dataiku DSS before 4.2.3 allows remote attackers to obtain sensitive information (i.e., determine if a username is valid) because of profile pictures visibility.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.