A vulnerability in haserl, a component of the Alpine Linux Configuration Framework before version 0.9.36, allows local users to read the contents of any file on the filesystem due to a lack of proper verification. The flaw arises from insufficient access control or input validation, enabling 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 single Metasploit post-exploitation module targeting the haserl utility on Linux systems (prior to version 0.9.36, CVE-2021-29133). The module is designed to be run after gaining a shell or meterpreter session on a target. It searches for setuid haserl-lua binaries in /usr/bin, and if found, uses them to read arbitrary files (default: /etc/shadow). The contents of the file are then saved as loot for later analysis. The exploit is operational, requiring a specific local configuration (presence of a vulnerable setuid binary) and does not provide remote code execution, but rather arbitrary file read capabilities. The code is written in Ruby and is structured as a standard Metasploit post module.
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.