# CVE-2023-33190: Improperly configured permissions in Sealos

> Attackers can gain cluster control permissions due to improper RBAC configuration, allowing full control over the Sealos cloud operating system and its resources.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** Yes
- **Published:** 29 Jun 2023
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-74j8-w7f9-pp62

## What is CVE-2023-33190?

CVE-2023-33190 is a critical missing authorization vulnerability in labring sealos, published on 29 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sealos is an open source cloud operating system distribution based on the Kubernetes kernel. In versions of Sealos prior to 4.2.1-rc4 an improper configuration of role based access control (RBAC) permissions resulted in an attacker being able to obtain cluster control permissions, which could control the entire cluster deployed with Sealos, as well as hundreds of pods and other resources within the cluster. This issue has been addressed in version 4.2.1-rc4. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-863 (Incorrect Authorization), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-33190?

2 open source packages ship an affected version, including github.com/labring/sealos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/labring/sealos` | Go | All versions | 4.2.1-rc4 |
| `github.com/labring/sealos` | Go | All versions | 4.2.1-rc4 |

Products: Sealos Project Sealos.

## How do I fix CVE-2023-33190?

Upgrade github.com/labring/sealos to 4.2.1-rc4 or later.

## Is CVE-2023-33190 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33190 and fix it if it is affected.

What it is: CVE-2023-33190 is a critical missing authorization vulnerability in labring sealos, published on 29 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33190 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/labring/sealos (Go): affected all versions; fixed in 4.2.1-rc4
- github.com/labring/sealos (Go): affected all versions; fixed in 4.2.1-rc4

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-2023-33190/ (Markdown: https://insights.sbomify.com/CVE-2023-33190/index.md)
```

## Sources

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

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