Sealos up to 4.1.x Role Based Access Control improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Sealos up to 4.1.x. Affected by this vulnerability is an unknown functionality of the component Role Based Access Control. This manipulation causes improper authentication. This vulnerability is registered as CVE-2023-33190. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical was found in Sealos up to 4.1.x. Affected by this vulnerability is an unknown code of the component Role Based Access Control. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Sealos is an open source cloud operating system distribution based on the Kubernetes kernel. In versions of Sealos prior to 4.2.0 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.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.
The weakness was published 06/29/2023 as GHSA-74j8-w7f9-pp62. The advisory is shared at github.com. This vulnerability is known as CVE-2023-33190 since 05/17/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.2.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.5VulDB Meta Temp Score: 9.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.9
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Sealos 4.2.0
Patch: github.com
Timeline
05/17/2023 🔍06/29/2023 🔍
06/29/2023 🔍
07/21/2023 🔍
Sources
Advisory: GHSA-74j8-w7f9-pp62Status: Confirmed
CVE: CVE-2023-33190 (🔍)
GCVE (CVE): GCVE-0-2023-33190
GCVE (VulDB): GCVE-100-232705
Entry
Created: 06/29/2023 22:14Updated: 07/21/2023 14:37
Changes: 06/29/2023 22:14 (50), 07/21/2023 14:33 (1), 07/21/2023 14:37 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.