In Lightdash before version 0.510.3, the file endpoints implemented in packages/backend/src/routers are vulnerable to directory traversal attacks. The endpoints do not properly sanitize user-supplied input, allowing attackers to use '..' sequences to access files outside the intended directory. Additionally, the endpoints do not enforce that only files with specific extensions (.csv or .png) are accessed, further increasing the risk of unauthorized file access.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python proof-of-concept exploit for CVE-2023-35844, a path traversal vulnerability in Lightdash. The main file, CVE-2023-35844.py, allows the user to test a single URL or a list of URLs for the vulnerability. The exploit works by sending a GET request to the vulnerable API endpoint '/api/v1/slack/image/slack-image%2F..%2F..%2F..%2Fetc%2Fpasswd', attempting to read the /etc/passwd file from the server. If the file is successfully read and contains the string 'root', the script prints the file contents, confirming the vulnerability. The README provides a brief description in Chinese, identifying the exploit as a file read vulnerability for Lightdash. The exploit is network-based and targets Lightdash instances accessible over HTTP/HTTPS.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.