CVE-2010-20112 is a stack-based buffer overflow in Amlib NetOpacs webquery.dll. The flaw is triggered by improper handling of HTTP GET parameters, specifically insufficient bounds checking on data supplied to the app parameter. An attacker can send an overly long value that overwrites stack memory, including the Structured Exception Handler (SEH), leading to memory corruption and potential control of execution flow. The provided context also indicates that malformed parameter names followed by an equals sign may cause unintended control-flow behavior. The vulnerable component is exposed via IIS on legacy Windows deployments.
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 module targeting a stack buffer overflow vulnerability in Amlib's Amlibweb NetOpacs (webquery.dll) component, accessible via HTTP requests on Windows systems (notably Windows 2000 with IIS5). The exploit works by sending an overly long 'app' parameter to the webquery.dll endpoint, overwriting SEH and allowing for arbitrary code execution. The module supports customizable payloads via the Metasploit framework, enabling actions such as reverse shells. The code includes a check method to verify vulnerability and an exploit method to deliver the payload. The only fingerprintable endpoint is '/amlibweb/webquery.dll', which is targeted via HTTP GET requests. The repository is operational and suitable for real-world exploitation within the constraints of the targeted software and platform.
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.