Kubernetes kube-apiserver Request confused deputy

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.6$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Kubernetes. This impacts the function MutatingWebhookConfiguration/ValidatingWebhookConfiguration of the component kube-apiserver Request Handler. The manipulation leads to confused deputy. This vulnerability is referenced as CVE-2020-8561. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Kubernetes (Virtualization Software) (the affected version is unknown). It has been rated as problematic. This issue affects the function MutatingWebhookConfiguration/ValidatingWebhookConfiguration of the component kube-apiserver Request Handler. The manipulation with an unknown input leads to a confused deputy vulnerability. Using CWE to declare the problem leads to CWE-441. The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. Impacted is confidentiality.

The weakness was published 09/21/2021 as 10472. The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-8561 since 02/03/2020. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.6
VulDB Meta Temp Score: 3.6

VulDB Base Score: 2.7
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.1
NVD Vector: 🔍

CNA Base Score: 4.1
CNA Vector (Kubernetes): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Confused deputy
CWE: CWE-441
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/03/2020 🔍
09/21/2021 +595 days 🔍
09/21/2021 +0 days 🔍
06/02/2026 +1715 days 🔍

Sourcesinfo

Product: github.com

Advisory: 10472
Status: Confirmed

CVE: CVE-2020-8561 (🔍)
GCVE (CVE): GCVE-0-2020-8561
GCVE (VulDB): GCVE-100-183005

Entryinfo

Created: 09/21/2021 08:52
Updated: 06/02/2026 04:29
Changes: 09/21/2021 08:52 (47), 09/29/2021 18:13 (1), 06/02/2026 04:29 (33)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!