# CVE-2020-10587: Privilege escalation in n/a

> Local users can gain root access in antiX and MX Linux due to insecure Sudo configuration allowing arbitrary command execution.

- **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:** No
- **Published:** 14 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j889-m9mj-xrmv

## What is CVE-2020-10587?

CVE-2020-10587 is a high-severity vulnerability in n/a, published on 14 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

antiX and MX Linux allow local users to achieve root access via "persist-config --command /bin/sh" because of the Sudo configuration.

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

It affects 2 products.


Products: Antixlinux Antix Linux, Mxlinux Mx Linux.

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

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

## Is CVE-2020-10587 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10587 is a high-severity vulnerability in n/a, published on 14 Mar 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-10587 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-2020-10587/ (Markdown: https://insights.sbomify.com/CVE-2020-10587/index.md)
```

## Sources

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

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