# CVE-2023-30969: Palantir Tiles missing authentication on API endpoints

> Attackers can access Palantir Tiles API endpoints without authentication, potentially reading or modifying data.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2023
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-f257-8wpr-74j7

## What is CVE-2023-30969?

CVE-2023-30969 is a high-severity missing authorization vulnerability in com.palantir.tiles:tiles, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Palantir Tiles1 service was  found to be vulnerable to an API wide issue where the service was not performing authentication/authorization on all the endpoints.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2023-30969?

It affects 1 product.


Products: Palantir Tiles.

## How do I fix CVE-2023-30969?

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

## Is CVE-2023-30969 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30969 and fix it if it is affected.

What it is: CVE-2023-30969 is a high-severity missing authorization vulnerability in com.palantir.tiles:tiles, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30969 in the wild and no public exploit code.

Affected product: com.palantir.tiles:tiles. 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-2023-30969/ (Markdown: https://insights.sbomify.com/CVE-2023-30969/index.md)
```

## Sources

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

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