Loading vulnerability…
qSnapper before 1.3.3 exposed multiple snapshot diff-related D-Bus methods under the weaker list-snapshots Polkit action, which was allowed for locally logged-in users without authentication. As a result, local users could invoke methods including ListSnapshots(), GetFileChanges(), GetFileDiffAndDetails(), GetFileChangesBetween(), and GetFileDiffBetween() against snapshots managed by the privileged qsnapper-dbus-service running as root. These methods disclosed metadata changes for arbitrary files between snapshots or between a snapshot and the live filesystem, and GetFileDiffBetween() could return full file-content diffs. This created a local information disclosure vulnerability that allowed access to otherwise read-protected information, including sensitive files such as /etc/shadow or files in root’s home directory.
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.
view-diff Polkit action protected with auth_admin, separating diff access from the less-privileged snapshot-listing capability.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.