# CVE-2020-10008: A logic issue was addressed with improved restrictions.


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-38r4-7ccg-8f66

## What is CVE-2020-10008?

CVE-2020-10008 is a medium-severity vulnerability in Apple Macos, published on 2 Apr 2021. 

### Official description

A logic issue was addressed with improved restrictions. This issue is fixed in macOS Big Sur 11.0.1. A malicious application with root privileges may be able to access private information.

## Which versions are affected by CVE-2020-10008?

It affects 1 product.


Products: Apple Macos.

## How do I fix CVE-2020-10008?

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

## Is CVE-2020-10008 being exploited?

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

## Other vulnerabilities in Apple Macos

- [CVE-2026-65400](https://insights.sbomify.com/CVE-2026-65400/): Apple macOS Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2024-44146](https://insights.sbomify.com/CVE-2024-44146/): Security feature bypass in macOS (critical 10.0)
- [CVE-2024-44148](https://insights.sbomify.com/CVE-2024-44148/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-38586](https://insights.sbomify.com/CVE-2023-38586/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-40455](https://insights.sbomify.com/CVE-2023-40455/): Security feature bypass in macOS (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10008 and fix it if it is affected.

What it is: CVE-2020-10008 is a medium-severity vulnerability in Apple Macos, published on 2 Apr 2021. 
Exploitation: There is no known exploitation of CVE-2020-10008 in the wild and no public exploit code.

Affected product: Apple Macos. 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-2020-10008/ (Markdown: https://insights.sbomify.com/CVE-2020-10008/index.md)
```

## Sources

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

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