CVE-2023-41044 is a partial path traversal vulnerability in Graylog's Support Bundle feature. The issue is caused by insufficient validation of user-supplied input in an HTTP API resource handling support bundle file operations. An attacker with valid Graylog Admin role credentials can abuse the affected API endpoints to access files outside the intended support bundle directory, specifically in sibling directories whose names begin with the support bundle directory path. In default DEB/RPM installations, Graylog's data directory is /var/lib/graylog-server and the Support Bundle directory is <data_dir>/support-bundle, allowing access to files in directories such as /var/lib/graylog-server/support-bundle-test or /var/lib/graylog-server/support-bundlesdirectory. In Graylog Docker images, the default data_dir is /usr/share/graylog/data, with the same support-bundle subdirectory pattern. The vulnerable functionality is exposed through the HTTP API endpoints GET /api/system/debug/support/bundle/download/{filename} and DELETE /api/system/debug/support/bundle/{filename}.
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.
support-bundle prefix. This can result in unauthorized read access to local files and unauthorized deletion of files, affecting confidentiality and integrity. Based on the provided information, the impact is limited to file read and file deletion within matching sibling directories; arbitrary code execution is not indicated.If you can’t patch tonight, do this now.
GET /api/system/debug/support/bundle/download/{filename} and DELETE /api/system/debug/support/bundle/{filename}.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.