{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50253 exists.","fix":"No fix has been published for CVE-2023-50253 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50253 is a critical missing authorization vulnerability in labring laf, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-50253 and fix it if it is affected.\n\nWhat it is: CVE-2023-50253 is a critical missing authorization vulnerability in labring laf, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50253 exists.\n\nAffected product: labring laf. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-50253/ (Markdown: https://insights.sbomify.com/CVE-2023-50253/index.md)","id":"CVE-2023-50253","markdown":"https://insights.sbomify.com/CVE-2023-50253/index.md","name":"CVE-2023-50253","record":{"aliases":["GHSA-g9c8-wh35-g75f"],"analysis":{"component_type":"cloud_service","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Laf cloud platform","requires_auth":"none","summary":"Authenticated users can access logs from any pod in the same namespace due to missing permission checks, exposing sensitive information.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"laf","vendor":"laf"}],"cvss":{"score":9.7,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"laf logs leak","id":"CVE-2023-50253","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Deepin Reader RCE vulnerability due to a design flaw","id":"CVE-2023-50254"},"packages":[],"prev":{"headline":"php-svg-lib unsafe attributes merge when parsing `use` tag","id":"CVE-2023-50252"},"products":["laf"],"published":"2024-01-03","related":[{"cvss_score":8.9,"headline":"Laf env causes sensitive information disclosure","id":"CVE-2023-48225","kev_date_added":null,"published":"2023-12-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-09","vendors":["labring"]},"summary":"Authenticated users can access logs from any pod in the same namespace due to missing permission checks, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2023-50253/"}