Loading vulnerability…
CVE-2016-9299 affects the Jenkins remoting module in Jenkins before 2.32 and LTS before 2.19.3. The vulnerability allows remote attackers to execute arbitrary code by supplying a crafted serialized Java object. Deserialization of the attacker-controlled object can trigger an LDAP query to a third-party server, leading to unsafe handling of attacker-influenced data in the LDAP lookup path and ultimately arbitrary code execution.
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: 'jenkins_ldap_deserialize.rb', which targets Jenkins servers (<=2.31) running on Linux with the LDAP plugin enabled. The exploit leverages a Java deserialization vulnerability in the way Jenkins processes LDAP responses. The module works by setting up a malicious LDAP server that delivers a crafted Java serialized object (payload) to the Jenkins server. When Jenkins connects to the LDAP server (as part of authentication or user lookup), the malicious payload is deserialized, resulting in arbitrary code execution on the Jenkins server. The module includes hardcoded serialized payloads (STAGE1 and STAGE2) and demonstrates command execution by creating a file ('/tmp/wtf'). The exploit interacts with the Jenkins server over HTTP to check for vulnerability and trigger the exploit. The code is written in Ruby and is designed to be used within the Metasploit framework. No CVE is explicitly referenced, but the exploit is operational and provides remote code execution capabilities.
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.