Loading vulnerability…
CVE-2023-34634 affects Greenshot 1.2.10 and earlier. The vulnerability arises because .NET content embedded in a .greenshot file is insecurely deserialized when the file is opened. This unsafe deserialization condition allows attacker-controlled serialized data to be processed by the application without adequate validation or restriction, enabling execution of arbitrary code in the context of the user running Greenshot.
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 (1 hidden).
This repository contains a single Metasploit module targeting a .NET deserialization vulnerability (CVE-2023-34634) in Greenshot version 1.3.274 and below on Windows. The exploit works by generating a malicious Greenshot file (with a .greenshot extension) that embeds a .NET deserialization payload. When a victim opens this file in Greenshot, arbitrary commands are executed with the privileges of the user running the application. The module allows the attacker to specify a base PNG file or use a default one, appends the deserialization payload, and creates a file that can be delivered to the target. The attack vector is local, requiring user interaction to open the crafted file. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads.
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.