cve.bz

CVE-2023-48225 laf laf

9.1 criticalExploit referenceEPSS 0.8%

Critical (9.1) in laf laf. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2023-48225 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-48225?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-48225?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-48225 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
laf:laf0.1.5
laf:laf0.4.0
laf:laf0.4.1
laf:laf0.4.2
laf:laf0.4.3
laf:laf0.4.4
laf:laf0.4.5
laf:laf0.4.6
laf:laf0.4.7
laf:laf0.4.8
laf:laf0.4.9
laf:laf0.4.10
laf:laf0.4.11
laf:laf0.4.12
laf:laf0.4.13
laf:laf0.4.14
laf:laf0.4.15
laf:laf0.4.16
laf:laf0.4.17
laf:laf0.4.18
laf:laf0.4.19
laf:laf0.4.20
laf:laf0.4.21:alpha0
laf:laf0.5.0
laf:laf0.5.0:alpha0
laf:laf0.5.0:alpha1
laf:laf0.5.0:alpha2
laf:laf0.5.0:alpha3
laf:laf0.5.1
laf:laf0.5.1:alpha0
laf:laf0.5.2
laf:laf0.5.2:alpha0
laf:laf0.5.3
laf:laf0.5.4
laf:laf0.5.4:alpha0
laf:laf0.5.5
laf:laf0.5.5:alpha0
laf:laf0.5.6
laf:laf0.5.7
laf:laf0.5.7:alpha0
laf:laf0.5.8:alpha0
laf:laf0.6.0
laf:laf0.6.0:alpha0
laf:laf0.6.0:alpha1
laf:laf0.6.0:alpha10
laf:laf0.6.0:alpha2
laf:laf0.6.0:alpha3
laf:laf0.6.0:alpha4
laf:laf0.6.0:alpha5
laf:laf0.6.0:alpha6
laf:laf0.6.0:alpha7
laf:laf0.6.0:alpha8
laf:laf0.6.0:alpha9
laf:laf0.6.1
laf:laf0.6.2
laf:laf0.6.3
laf:laf0.6.4
laf:laf0.6.5
laf:laf0.6.6
laf:laf0.6.7
laf:laf0.6.8
laf:laf0.6.9
laf:laf0.6.10
laf:laf0.6.11
laf:laf0.6.12
laf:laf0.6.13
laf:laf0.6.14
laf:laf0.6.15
laf:laf0.6.16
laf:laf0.6.17
laf:laf0.6.18
laf:laf0.6.19
laf:laf0.6.20
laf:laf0.6.21
laf:laf0.6.22
laf:laf0.6.23
laf:laf0.7.0
laf:laf0.7.1
laf:laf0.7.2
laf:laf0.7.3
laf:laf0.7.4
laf:laf0.7.5
laf:laf0.7.6
laf:laf0.7.7
laf:laf0.7.8
laf:laf0.7.9
laf:laf0.7.10
laf:laf0.7.11
laf:laf0.8.0
laf:laf0.8.0:alpha0
laf:laf0.8.0:alpha1
laf:laf0.8.0:alpha10
laf:laf0.8.0:alpha11
laf:laf0.8.0:alpha2
laf:laf0.8.0:alpha3
laf:laf0.8.0:alpha4
laf:laf0.8.0:alpha5
laf:laf0.8.0:alpha6
laf:laf0.8.0:alpha7
laf:laf0.8.0:alpha8
laf:laf0.8.0:alpha9
laf:laf0.8.1
laf:laf0.8.2
laf:laf0.8.3
laf:laf0.8.4
laf:laf0.8.5
laf:laf0.8.5:alpha0
laf:laf0.8.6
laf:laf0.8.7
laf:laf0.8.7:alpha0
laf:laf0.8.7:alpha1
laf:laf0.8.7:alpha2
laf:laf0.8.7:alpha3
laf:laf0.8.8
laf:laf0.8.9
laf:laf0.8.10
laf:laf0.8.11
laf:laf0.8.12
laf:laf0.8.13
laf:laf1.0.0:alpha0
laf:laf1.0.0:alpha1
laf:laf1.0.0:alpha2
laf:laf1.0.0:alpha3
laf:laf1.0.0:alpha4
laf:laf1.0.0:alpha5
laf:laf1.0.0:alpha6
laf:laf1.0.0:beta0
laf:laf1.0.0:beta1
laf:laf1.0.0:beta10
laf:laf1.0.0:beta11
laf:laf1.0.0:beta12
laf:laf1.0.0:beta13
laf:laf1.0.0:beta2
laf:laf1.0.0:beta3
laf:laf1.0.0:beta4
laf:laf1.0.0:beta5
laf:laf1.0.0:beta6
laf:laf1.0.0:beta7
laf:laf1.0.0:beta8
laf:laf1.0.0:beta9

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON