Approved changes feed: RSS · Atom

cpe:2.3:a:laf:laf:0.5.0:alpha2:*:*:*:*:*:*

part: a version: 0.5.0 update: alpha2

VendorLaf (80bec146-37e2-54e6-a003-037d058fcc8d)
ProductLaf (ae32b98b-869d-509a-ad94-908d46880f2c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/labring/laf purl2cpe 2026-06-01 10:11:22.680063

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-50253 vulnerable 2026-06-08 06:16:15.773302 laf logs leak
CRITICAL (9.7)
Laf is a cloud development platform. In the Laf version design, the log uses communication with k8s to quickly retrieve logs from the container without the need for additional storage. However, in version 1.0.0-beta.13 and prior, this interface does not verify the permissions of the pod, which allows authenticated users to obtain any pod logs under the same namespace through this method, thereby obtaining sensitive information printed in the logs. As of time of publication, no known patched versions exist.
Published: 2024-01-03T16:45:11.778Z
Updated: 2025-06-09T18:48:18.796Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-48225 vulnerable 2026-06-08 06:14:26.209640 Laf env causes sensitive information disclosure
HIGH (8.9)
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.
Published: 2023-12-12T20:33:40.959Z
Updated: 2024-08-02T21:23:39.023Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.