Loading vulnerability…
CVE-2016-0790 (Jenkins SECURITY-241) is an observable timing discrepancy in Jenkins API-token verification. Jenkins versions earlier than 1.650 and Jenkins LTS versions earlier than 1.642.2 compared API tokens using a non-constant-time algorithm. Comparison duration could vary according to how much of an attacker-supplied token matched the valid token, enabling incremental recovery of API-token values through repeated timing measurements.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Jenkins API-token comparison issue caused by non-constant-time comparison.
A Jenkins API-token comparison flaw caused by non-constant-time comparison.
A Jenkins security vulnerability addressed by upgrading Jenkins to upstream version 1.642.2 LTS in the Red Hat OpenShift Enterprise 3.1 package and image update.
An important Jenkins API-token verification timing flaw. Non-constant-time token comparison in Jenkins versions before 1.650 and LTS versions before 1.642.2 can enable remote brute-force determination of API tokens.
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.