Loading vulnerability…
A buffer overflow exists in the readstr_upto function in plug-ins/script-fu/tinyscheme/scheme.c in GIMP versions 2.6.12 and earlier, and possibly 2.6.13. The vulnerability is triggered when a long string is sent in a command to the script-fu server, leading to a buffer overflow condition.
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 (modules/exploits/windows/misc/gimp_script_fu.rb) that exploits a buffer overflow vulnerability (CVE-2012-2763) in the script-fu server component of GIMP for Windows (versions <= 2.6.12). The exploit targets the TCP service typically running on port 10008. By sending a specially crafted packet containing a Metasploit payload, the attacker can overwrite function pointers in the .bss section of the script-fu server process, leading to remote code execution under the context of the user running GIMP. The module allows for customizable payloads (up to 1024 bytes, with certain bad characters filtered out) and is tested against GIMP 2.6.10 and 2.6.1 (no DEP) on Windows XP SP3 and Windows 7 SP1. The exploit is operational and provides remote shell access or arbitrary code execution if successful. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.
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.