Loading vulnerability…
CVE-2016-3725 (SECURITY-273) is a missing-authorization-check vulnerability in Jenkins update-site metadata refresh functionality. Jenkins versions before 2.3 and Jenkins LTS versions before 1.651.2 allow an authenticated user with Jenkins access to trigger downloads of update-site metadata without the intended permission.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Jenkins issue allowing regular users to trigger downloads of update-site metadata.
A Jenkins flaw allowing regular users to trigger downloads of update-site metadata.
A Jenkins security vulnerability addressed by upgrading the Jenkins continuous integration server to upstream version 1.651.2 LTS. The content does not map the specific flaw type to this individual CVE.
A low-severity Jenkins authorization flaw (SECURITY-273) that lets any user able to access Jenkins trigger downloads of update-site metadata. Combined with DNS cache poisoning, this could be used to disrupt Jenkins service.
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.