# CVE-2013-4201: Missing authorization in n/a

> Authenticated users can bypass permission checks to remove systems via CLI, leading to unauthorized data modification and privilege escalation.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** Yes
- **Published:** 1 May 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g43x-fhj2-4p43

## What is CVE-2013-4201?

CVE-2013-4201 is a medium-severity missing authorization vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Katello allows remote authenticated users to call the "system remove_deletion" CLI command via vectors related to "remove system" permissions.

Weakness: CWE-275

## Which versions are affected by CVE-2013-4201?

It affects 1 product.


Products: Katello Katello.

## How do I fix CVE-2013-4201?

Apply the vendor's patch.

## Is CVE-2013-4201 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-3072](https://insights.sbomify.com/CVE-2016-3072/): Katello SQL Injection vulnerabilities (high 8.8)
- [CVE-2014-3712](https://insights.sbomify.com/CVE-2014-3712/): Denial of service in n/a (medium 5.0)
- [CVE-2012-5561](https://insights.sbomify.com/CVE-2012-5561/): Information disclosure in n/a (low 2.1)
- [CVE-2012-6116](https://insights.sbomify.com/CVE-2012-6116/): Misconfiguration in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4201 and fix it if it is affected.

What it is: CVE-2013-4201 is a medium-severity missing authorization vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4201 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-2013-4201/ (Markdown: https://insights.sbomify.com/CVE-2013-4201/index.md)
```

## Sources

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

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