Security readout for executives and security teams
Plain-English summary
CVE-2023-36815 is a billing authorization flaw in Sealos 4.2.0 and earlier. A logged-in user may be able to manipulate the Payment custom resource and recharge an arbitrary 1 RMB amount, with possible exposure of resource information through the charging interface. The sources do not confirm a fix.
Executive priority
Treat this as a high-priority business integrity issue for affected Sealos environments. The main risk is unauthorized billing manipulation and possible resource information disclosure. Because the public sources do not confirm a fix, prioritize exposure reduction, monitoring, and vendor guidance review.
Technical view
The issue is classified as CWE-862, missing authorization. The CVE describes insufficient permission control around sealos.io/v1/Payment in user-controlled namespaces, affecting labring Sealos versions up to 4.2.0. CVSS 3.1 is 7.3 high, with network reachability, low complexity, low privileges, and high confidentiality and integrity impact.
Likely exposure
Exposure is most likely in Sealos deployments running version 4.2.0 or earlier where the billing system is enabled and normal users can interact with namespace-scoped custom resources. The source does not establish exposure for later versions or deployments without billing functionality.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked as CISA KEV. The described abuse requires a user account or low-privileged access, and may require user interaction per the CVSS vector. Public evidence is limited to the advisory and CVE data.
Researcher notes
Evidence is narrow but specific: affected versions, resource type, CWE, and CVSS are provided. The fix status is unclear, and no exploit-in-the-wild evidence is cited. Validation should focus on RBAC, namespace scoping, billing paths, and whether affected Payment resources are user-controllable.
Mitigation direction
- Check the Sealos advisory and vendor channels for confirmed fixed versions or workarounds.
- Restrict who can create or modify Payment custom resources.
- Review RBAC around billing-related resources in user-controlled namespaces.
- Limit billing system access to trusted users until remediation is confirmed.
- Monitor recharge activity for abnormal 1 RMB transactions.
Validation and detection
- Inventory Sealos deployments and identify versions at or below 4.2.0.
- Confirm whether the Sealos billing system is enabled in each deployment.
- Review namespace permissions for sealos.io/v1 Payment resources.
- Examine billing and recharge records for suspicious low-value transactions.
- Check whether charging interfaces expose resource information to unauthorized users.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-36815 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N2.15.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/labring/sealos/security/advisories/GHSA-vpxf-q44g-w34wCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.