Loading vulnerability…
GeoServer versions prior to 2.23.4 and 2.24.1 contain an arbitrary file upload condition in the REST Coverage Store API. An authenticated administrator with permissions to modify coverage stores can upload attacker-controlled file contents to attacker-chosen filesystem locations. The issue arises from inconsistent path traversal validation between GeoServer Resource implementations: coverage stores configured with relative paths use a Resource implementation that validates and blocks traversal, while coverage stores configured with absolute paths use a different Resource implementation that does not prevent path traversal. This enables writing arbitrary files and can lead to remote code execution; it may also allow overwriting GeoServer security configuration files to escalate privileges to full administrator.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.