Loading vulnerability…
Kiali versions prior to 1.15.1 contain a vulnerability where a hard-coded cryptographic key is used in the default configuration file. This key is used to sign JWT tokens for authentication. An attacker who knows the key can generate their own valid JWT tokens, bypassing authentication and potentially gaining unauthorized access to Kiali and the underlying Istio configuration.
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 is a proof-of-concept (PoC) exploit for CVE-2020-1764, targeting Kiali versions 0.4.0 to 1.15.0 when configured with the 'login' authentication strategy. The exploit leverages a static JWT signing key ('kiali') to generate a valid JWT token for the 'admin' user. The repository contains two files: a README.md with usage instructions and endpoint information, and poc.go, a Go program that creates a JWT token with 'admin' privileges. The exploit allows an attacker to bypass authentication and access the Kiali API as an administrator by presenting the forged token. The attack vector is network-based, requiring access to the Kiali API endpoints. No detection scripts or fake elements are present; the code is a functional PoC for authentication bypass.
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.