dbcve.org
Bored AgentApplication · Mirantis

CVE-2022-0270

HIGH · 8.8 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 0.6.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The bored-agent component prior to v0.6.1 lacks proper validation of incoming Kubernetes impersonation headers, allowing attackers to bypass authorization controls by supplying malicious username and group values that override the assigned identities.

MitigationUpgrade bored-agent to v0.6.1 or later which implements proper sanitization of Kubernetes impersonation headers. If immediate upgrade is not possible, implement upstream API gateway validation of impersonation headers before they reach bored-agent.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bored AgentApplication
Affected:< 0.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Mirantis Bored Agent is installed
    Search for the bored-agent binary or service on nodes: look for 'bored-agent' in /usr/local/bin/, /usr/bin/, or check running processes with 'ps aux | grep bored-agent'. Also check Kubernetes DaemonSets or systemD services.
    Affected if bored-agent binary or service is found running on any node
  2. Determine installed bored-agent version
    Run 'bored-agent --version' or check the image tag if deployed as a container: 'docker images' or 'crictl images' to find the bored-agent image and its tag.
    Affected if version is below 0.6.1 or the image has no version tag (latest, empty)
  3. Check if bored-agent receives direct API requests
    Examine the network configuration or ingress to determine if bored-agent is exposed to untrusted network paths. Review any proxy or gateway configurations that forward requests to bored-agent. Look for direct pod-to-pod communication without an API gateway.
    Affected if bored-agent is directly accessible without an upstream API gateway or validation layer filtering impersonation headers
  4. Inspect if impersonation headers can reach bored-agent
    Review your authentication/authorization proxy or API gateway configuration to see if X-Remote-User, Impersonate-User, Impersonate-Group, or similar Kubernetes impersonation headers are forwarded to bored-agent without validation.
    Affected if impersonation headers are passed through to bored-agent without being validated or sanitized upstream

You are affected if Mirantis Bored Agent version is below 0.6.1 AND the component receives Kubernetes impersonation headers from untrusted sources without upstream validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.6.1 or later
Fixed in 0.6.1
Interim mitigation

Upgrade bored-agent to v0.6.1 or later which implements proper sanitization of Kubernetes impersonation headers. If immediate upgrade is not possible, implement upstream API gateway validation of impersonation headers before they reach bored-agent.

Recommended fix High confidence

v0.6.1

  1. 1. Identify the deployment method used for bored-agent (e.g., Kubernetes Deployment, Helm chart, or binary)
  2. 2. If using a Kubernetes Deployment, edit the deployment: kubectl edit deployment <bored-agent-deployment> -n <namespace>
  3. 3. Update the container image to the fixed version: bored-agent:v0.6.1 or bored-agent:0.6.1
  4. 4. If using a Helm chart, run: helm upgrade <release-name> <chart-name> --set image.tag=0.6.1
  5. 5. Verify the new pods are running: kubectl get pods -n <namespace>
  6. 6. Ensure the application is functioning correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bored Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0270 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data