Skip to content

Sealos billing system permission control defect

High severity GitHub Reviewed Published Jun 30, 2023 in labring/sealos • Updated Nov 7, 2023

Package

gomod github.com/labring/sealos (Go)

Affected versions

<= 4.2.0

Patched versions

None

Description

Summary

There is a permission flaw in the Sealos billing system, which allows users to control the recharge resource account. sealos. io/v1/Payment, resulting in the ability to recharge any amount of 1 RMB.

Details

The reason is that sealos is in arrears. Egg pain, we can't create a terminal anymore. Let's charge for it:

Then it was discovered that the charging interface had returned all resource information. Unfortunately, based on previous vulnerability experience, the namespace of this custom resource is still under the current user's control and may have permission to correct it.

PoC

disable by publish

Impact

  • sealos public cloud user
  • CWE-287 Improper Authentication

References

@zzjin zzjin published to labring/sealos Jun 30, 2023
Published to the GitHub Advisory Database Jun 30, 2023
Reviewed Jun 30, 2023
Published by the National Vulnerability Database Jul 3, 2023
Last updated Nov 7, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

EPSS score

0.057%
(25th percentile)

Weaknesses

CVE ID

CVE-2023-36815

GHSA ID

GHSA-vpxf-q44g-w34w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.