Loading vulnerability…
CVE-2021-40822 is a server-side request forgery vulnerability in GeoServer affecting versions through 2.18.5 and 2.19.0 through 2.19.2. The issue is exposed through the option for setting a proxy host, which can be abused to cause the GeoServer instance to initiate attacker-influenced outbound requests. This allows untrusted input associated with proxy configuration to be used in a way that can redirect server-side network access to unintended destinations.
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 provides a proof-of-concept exploit for CVE-2021-40822, a Server-Side Request Forgery (SSRF) vulnerability in GeoServer. The main exploit script, CVE-2021-40822.py, is a Python tool that first detects if a target is running GeoServer by checking for the /geoserver/web/ endpoint. If GeoServer is detected, it attempts to exploit the SSRF by sending a POST request to /geoserver/TestWfsPost with a user-supplied URL parameter. The script checks the response for evidence that the server made a request to the attacker-controlled URL, confirming the vulnerability. The repository also includes a large number of sample data files and configuration files related to GeoServer, but the exploit logic is contained solely in the Python script. The exploit is a POC and does not provide a weaponized or post-exploitation payload, but demonstrates the ability to leverage the SSRF for further attacks. The attack vector is network-based, requiring access to the GeoServer HTTP interface.
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.
1 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.