Loading vulnerability…
CVE-2022-24847 affects GeoServer, an open-source Java-based geospatial data server. The vulnerability arises from GeoServer performing unchecked JNDI lookups in multiple administrative configuration paths. According to the provided content, this can occur in the GeoServer security mechanism, during configuration of data stores that use JNDI-backed data sources, and while configuring the disk quota mechanism. Because unsafe JNDI resolution can lead to attacker-controlled class loading and Java deserialization, a successful exploit can result in arbitrary code execution on the GeoServer host. Exploitation requires the attacker to make administrative changes through either the GeoServer web GUI or the REST API.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A GeoServer JNDI lookup remote code execution vulnerability that remains among the top actively targeted CVEs in the telemetry discussed.
Remote code execution vector described as a JNDI lookup issue in GeoServer.
Remote code execution in GeoServer via JNDI lookup behavior as described in the content.
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.