Loading vulnerability…
A buffer overflow vulnerability exists in PSOProxy version 0.91 due to improper handling of long HTTP requests. Specifically, the vulnerability can be triggered by sending an excessively long GET argument or method name, which can overflow internal buffers.
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 (4 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits a stack buffer overflow vulnerability in the PSO Proxy v0.91 web server (CVE-2004-0313). The exploit targets Windows 2000 and Windows XP systems running the vulnerable version of PSO Proxy, typically on TCP port 8080. The module works by sending an overly long string to the server, overwriting the stack and allowing execution of arbitrary code. The payload is customizable via Metasploit and can be used to gain remote code execution on the target. The module includes a check method to verify if the target is running the vulnerable version by inspecting the HTTP banner. The exploit is operational and can be used to compromise affected systems if properly configured.
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.