# CVE-2021-36758: Privilege escalation in n/a

> Attackers can create Secrets Automation access tokens with excessive permissions, leading to privilege escalation within the 1Password Connect server.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A: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:** 15 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r2xx-fjfv-4589

## What is CVE-2021-36758?

CVE-2021-36758 is a medium-severity vulnerability in n/a, published on 15 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

1Password Connect server before 1.2 is missing validation checks, permitting users to create Secrets Automation access tokens that can be used to perform privilege escalation. Malicious users authorized to create Secrets Automation access tokens can create tokens that have access beyond what the user is authorized to access, but limited to the existing authorizations of the Secret Automation the token is created in.

Weakness: CWE-863 (Incorrect Authorization), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: 1password Connect.

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

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

## Is CVE-2021-36758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-36758 is a medium-severity vulnerability in n/a, published on 15 Jul 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-36758 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-36758/ (Markdown: https://insights.sbomify.com/CVE-2021-36758/index.md)
```

## Sources

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

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