# CVE-2023-36815: Sealos billing system permission control defect

> Attackers can manipulate billing resources to recharge arbitrary amounts and potentially expose sensitive resource information due to missing authorization checks.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jul 2023
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-vpxf-q44g-w34w

## What is CVE-2023-36815?

CVE-2023-36815 is a high-severity missing authorization vulnerability in labring sealos, published on 3 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Sealos is a Cloud Operating System designed for managing cloud-native applications. In version 4.2.0 and prior, 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 renminbi (RMB). The charging interface may expose resource information. The namespace of this custom resource would be user's control and may have permission to correct it. It is not clear whether a fix exists.

Weakness: CWE-862 (Missing Authorization)

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

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 to 4.2.0 | None |
| `github.com/labring/sealos` | Go | All versions to 4.2.0 | None |

Products: Sealos Sealos.

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

No fix has been published for CVE-2023-36815 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-36815 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36815 is a high-severity missing authorization vulnerability in labring sealos, published on 3 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-36815 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/labring/sealos (Go): affected all versions up to 4.2.0; no fix listed
- github.com/labring/sealos (Go): affected all versions up to 4.2.0; no fix listed

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

## Sources

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

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