CVE-2022-24726: Unauthenticated control plane denial of service attack in Istio
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: kiali (Red Hat:service_mesh:2.0::el8) 0:v1.24.7.redhat1-1.el8; servicemesh (Red Hat:service_mesh:2.0::el8) 0:2.0.9-3.el8; servicemesh-istioctl (Red Hat:service_mesh:2.0::el8) 0:2.0.9-3.el8.
Low priority for now. Upgrade to kiali (Red Hat:service_mesh:2.0::el8) 0:v1.24.7.redhat1-1.el8; servicemesh (Red Hat:service_mesh:2.0::el8) 0:2.0.9-3.el8; servicemesh-istioctl (Red Hat:service_mesh:2.0::el8) 0:2.0.9-3.el8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Istio is an open platform to connect, manage, and secure microservices. In affected versions the Istio control plane, istiod, is vulnerable to a request processing error, allowing a malicious attacker that sends a specially crafted message which results in the control plane crashing when the validating webhook for a cluster is exposed publicly. This endpoint is served over TLS port 15017, but does not require any authentication from the attacker. For simple installations, Istiod is typically only reachable from within the cluster, limiting the blast radius. However, for some deployments, especially [external istiod](https://istio.io/latest/docs/setup/install/external-controlplane/) topologies, this port is exposed over the public internet. This issue has been patched in versions 1.13.2, 1.12.5 and 1.11.8. Users are advised to upgrade. Users unable to upgrade should disable access to a validating webhook that is exposed to the public internet or restrict the set of IP addresses that can query it to a set of known, trusted entities.
- Published
- Mar 10, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.5% · 75th percentile
- CWE
- CWE-400
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| istio | istio | cpe:2.3:a:istio:istio |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- istio istiobefore 1.11.8
- istio istio1.12.0 and later · before 1.12.5
- istio istio1.13.0 and later · before 1.13.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
istio istio
- < 1.11.8,, >= 1.12.0, < 1.12.5, >= 1.13.0, < 1.13.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:service_mesh:2.0::el8 | kiali | before 0:v1.24.7.redhat1-1.el8 | 0:v1.24.7.redhat1-1.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-istioctl | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-mixc | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-mixs | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-pilot-agent | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-pilot-discovery | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-prometheus | before 0:2.14.0-16.el8.1 | 0:2.14.0-16.el8.1 |
| Red Hat:service_mesh:2.0::el8 | servicemesh-proxy | before 0:2.0.9-3.el8 | 0:2.0.9-3.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-cni | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-pilot-agent | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-pilot-discovery | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-proxy | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-proxy-debuginfo | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-proxy-debugsource | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
| Red Hat:service_mesh:2.1::el8 | servicemesh-proxy-wasm | before 0:2.1.2-4.el8 | 0:2.1.2-4.el8 |
Same product
istio: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-31045Ill-formed headers may lead to unexpected behavior in Istio39Monitor
- CVE-2022-21679Authorization Policy bypass in Istio39Monitor
- CVE-2021-31921Istio before 1.8.6 and 1.9.x before 1.9.5 contains a remotely exploitable vulnerability where an external client can access unexpected servi39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-21701Jan 19, 2022 · Privileged Escalation in Istio35Monitor
- ← EarlierCVE-2022-23635Feb 22, 2022 · Unauthenticated control plane denial of service attack in Istio30Monitor
- Later →CVE-2022-39278Oct 13, 2022 · Istio vulnerable to denial of service attack due to Golang Regex Library30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:kiali | 0:v1.24.7.redhat1-1.el8 · Red Hat:service_mesh:2.0::el8 | Package registry (OSV) |
| red hat:servicemesh | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-cni | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-istioctl | 0:2.0.9-3.el8 · Red Hat:service_mesh:2.0::el8 | Package registry (OSV) |
| red hat:servicemesh-mixc | 0:2.0.9-3.el8 · Red Hat:service_mesh:2.0::el8 | Package registry (OSV) |
| red hat:servicemesh-mixs | 0:2.0.9-3.el8 · Red Hat:service_mesh:2.0::el8 | Package registry (OSV) |
| red hat:servicemesh-pilot-agent | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-pilot-discovery | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-proxy | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-proxy-debuginfo | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-proxy-debugsource | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
| red hat:servicemesh-proxy-wasm | 0:2.1.2-4.el8 · Red Hat:service_mesh:2.1::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.