# CVE-2023-48225: Laf env causes sensitive information disclosure

> Attackers in privatized environments can read sensitive secrets and configmaps via Kubernetes envFrom due to improper environment variable handling.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L`)
- **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:** 12 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-hv2g-gxx4-fwxp

## What is CVE-2023-48225?

CVE-2023-48225 is a high-severity vulnerability in labring laf, published on 12 Dec 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

Laf is a cloud development platform. Prior to version 1.0.0-beta.13, the control of LAF app enV is not strict enough, and in certain scenarios of privatization environment, it may lead to sensitive information leakage in secret and configmap. In ES6 syntax, if an obj directly references another obj, the name of the obj itself will be used as the key, and the entire object structure will be integrated intact. When constructing the deployment instance of the app, env was found from the database and directly inserted into the template, resulting in controllability here. Sensitive information in the secret and configmap can be read through the k8s envFrom field. In a privatization environment, when `namespaceConf. fixed` is marked, it may lead to the leakage of sensitive information in the system. As of time of publication, it is unclear whether any patches or workarounds exist.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Laf Laf.

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

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

## Is CVE-2023-48225 being exploited?

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

## Other vulnerabilities in labring laf

- [CVE-2023-50253](https://insights.sbomify.com/CVE-2023-50253/): laf logs leak (critical 9.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-48225 is a high-severity vulnerability in labring laf, published on 12 Dec 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-48225 in the wild and no public exploit code.

Affected product: labring laf. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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