# CVE-2022-0270: Improper header sanitization in bored-agent causes escalation of privilege

> Attackers can escalate privileges by manipulating unsanitized Kubernetes impersonation headers in the bored-agent component.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r5c2-7hp9-v678

## What is CVE-2022-0270?

CVE-2022-0270 is a high-severity authentication bypass vulnerability in Mirantis bored-agent, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Prior to v0.6.1, bored-agent failed to sanitize incoming kubernetes impersonation headers allowing a user to override assigned user name and groups.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2022-0270?

It affects 1 product.


Products: Mirantis Bored-Agent.

## How do I fix CVE-2022-0270?

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

## Is CVE-2022-0270 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0270 and fix it if it is affected.

What it is: CVE-2022-0270 is a high-severity authentication bypass vulnerability in Mirantis bored-agent, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0270 in the wild and no public exploit code.

Affected product: Mirantis bored-agent. 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-2022-0270/ (Markdown: https://insights.sbomify.com/CVE-2022-0270/index.md)
```

## Sources

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

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