Cross-pod log disclosure via unchecked pod name
Published Jan 3, 2024 · Updated Jun 9, 2025
Information disclosure in Labring LAF 1.0.0-beta.13 and earlier allows remote authenticated users to read other pods' logs. The log API accepts a caller-controlled pod name after checking only JWT and application guards, without verifying that the requested pod belongs to the caller's application. A valid token and application ID within the shared namespace expose sensitive data written by other workloads to their container logs.
Summary
What happened
Information disclosure in Labring LAF 1.0.0-beta.13 and earlier allows remote authenticated users to read other pods' logs. The log API accepts a caller-controlled pod name after checking only JWT and application guards, without verifying that the requested pod belongs to the caller's application. A valid token and application ID within the shared namespace expose sensitive data written by other workloads to their container logs.
The record
- CVE
- CVE-2023-50253
- Published
- Jan 3, 2024
- Updated
- Jun 9, 2025
- Vendor
- Labring
- Product
- LAF
- Classifications
- CWE-532, CWE-200, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.0.0-beta.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo