# CVE-2020-10699: Privilege escalation in targetcli

> A local attacker can escalate privileges to root by modifying iSCSI configuration via a world-writable socket in targetcli-fb.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pvmm-475g-fx2h, RHSA-2020:1933, UBUNTU-CVE-2020-10699

## What is CVE-2020-10699?

CVE-2020-10699 is a high-severity vulnerability in Datera, Inc targetcli, published on 15 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in Linux, in targetcli-fb versions 2.1.50 and 2.1.51 where the socket used by targetclid was world-writable. If a system enables the targetclid socket, a local attacker can use this flaw to modify the iSCSI configuration and escalate their privileges to root.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `targetcli` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.51-4.el8_2 |

Products: Targetcli-Fb Project Targetcli-Fb.

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

Apply the vendor's patch.

## Is CVE-2020-10699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10699 is a high-severity vulnerability in Datera, Inc targetcli, published on 15 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10699 in the wild and no public exploit code.

Affected product: Datera, Inc targetcli. 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-10699/ (Markdown: https://insights.sbomify.com/CVE-2020-10699/index.md)
```

## Sources

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

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