CVE-2023-50253: labring laf · Information Exposure
Affects labring lafSource CVE Database V5
Not known to be exploited · CVSS 9.7 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublabring/lafpkg:github/labring/lafOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Implement strict Kubernetes Role-Based Access Control (RBAC) policies to limit which authenticated users can access pod logs within namespaces. Ensure that only trusted users have permissions to read logs.
- Use Kubernetes Network Policies and namespace segmentation to isolate sensitive workloads and reduce the blast radius of compromised accounts.
- Monitor and audit log access activities closely to detect any unauthorized attempts to retrieve pod logs.
- Consider disabling or restricting the Laf log retrieval interface if feasible until a patch is available.
- Employ secrets management best practices to avoid printing sensitive information in logs.
- Engage with the Laf vendor and community to track patch releases and apply updates promptly once available.
- Use multi-factor authentication (MFA) for all users accessing the platform to reduce the risk of compromised credentials being exploited.
- If possible, deploy additional logging and monitoring tools that provide more granular access controls and alerting capabilities for log access.
Description
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.