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

> An insecure permission flaw in the Tock OS kernel allows untrusted capsules to access arbitrary memory, potentially leading to privilege escalation or code execution.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 6 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9w77-7jq2-wgpf

## What is CVE-2018-1000660?

CVE-2018-1000660 is a high-severity missing authorization vulnerability in n/a, published on 6 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOCK version prior to commit 42f7f36e74088036068d62253e1d8fb26605feed. For example dfde28196cd12071fcf6669f7654be7df482b85d contains a Insecure Permissions vulnerability in Function get_package_name in the file kernel/src/tbfheader.rs, variable "pub package_name: &'static str," in the file process.rs that can result in A tock capsule (untrusted driver) could access arbitrary memory by using only safe code. This vulnerability appears to have been fixed in commit 42f7f36e74088036068d62253e1d8fb26605feed.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Tockos Tock.

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

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

## Is CVE-2018-1000660 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000660 is a high-severity missing authorization vulnerability in n/a, published on 6 Sep 2018. 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-2018-1000660 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-1000660/ (Markdown: https://insights.sbomify.com/CVE-2018-1000660/index.md)
```

## Sources

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

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