# CVE-2021-27225: Missing authorization in n/a

> Users with coding permissions can read and overwrite notebooks in unauthorized projects due to insufficient access control in Dataiku DSS.

- **Severity:** Medium 5.4 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:L/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mp33-8vpj-672c

## What is CVE-2021-27225?

CVE-2021-27225 is a medium-severity missing authorization vulnerability in n/a, published on 1 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2021-27225?

It affects 1 product.


Products: Dataiku Data Science Studio.

## How do I fix CVE-2021-27225?

No fix has been published for CVE-2021-27225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-27225 being exploited?

There is no known exploitation of CVE-2021-27225 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-51717](https://insights.sbomify.com/CVE-2023-51717/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-8817](https://insights.sbomify.com/CVE-2020-8817/): Missing authorization in n/a (high 8.1)
- [CVE-2023-24045](https://insights.sbomify.com/CVE-2023-24045/): Path traversal in n/a (medium 6.5)
- [CVE-2018-10732](https://insights.sbomify.com/CVE-2018-10732/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27225 and fix it if it is affected.

What it is: CVE-2021-27225 is a medium-severity missing authorization vulnerability in n/a, published on 1 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27225 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-27225/ (Markdown: https://insights.sbomify.com/CVE-2021-27225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-27225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-27225
- OSV: https://osv.dev/vulnerability/CVE-2021-27225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-27225/
Summaries are generated and may contain mistakes; the official description above is the record.