# CVE-2018-10465: Missing authorization in n/a

> Authenticated users with limited privileges can access Universal API endpoints to read, modify, or delete data due to incorrect access control.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qm5m-j3mj-33hq

## What is CVE-2018-10465?

CVE-2018-10465 is a high-severity missing authorization vulnerability in n/a, published on 7 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jamf Pro 10.x before 10.3.0 has Incorrect Access Control. Jamf Pro user accounts and groups with access to log in to Jamf Pro had full access to endpoints in the Universal API (UAPI), regardless of account privileges or privilege sets. An authenticated Jamf Pro account without required privileges could be used to perform CRUD actions (GET, POST, PUT, DELETE) on UAPI endpoints, which could result in unauthorized information disclosure, compromised data integrity, and data loss. For a full listing of available UAPI endpoints and associated CRUD actions you can navigate to /uapi/doc in your instance of Jamf Pro.

## Which versions are affected by CVE-2018-10465?

It affects 1 product.


Products: Jamf Jamf.

## How do I fix CVE-2018-10465?

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

## Is CVE-2018-10465 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31224](https://insights.sbomify.com/CVE-2023-31224/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-39303](https://insights.sbomify.com/CVE-2021-39303/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2019-17076](https://insights.sbomify.com/CVE-2019-17076/): Deserialization in n/a (critical 9.8)
- [CVE-2021-40809](https://insights.sbomify.com/CVE-2021-40809/): Privilege escalation in n/a (high 8.8)
- [CVE-2021-35037](https://insights.sbomify.com/CVE-2021-35037/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10465 and fix it if it is affected.

What it is: CVE-2018-10465 is a high-severity missing authorization vulnerability in n/a, published on 7 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10465 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-2018-10465/ (Markdown: https://insights.sbomify.com/CVE-2018-10465/index.md)
```

## Sources

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

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