Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

CVE-2020-8558 Vulnerability Notice

Updated on 2024-07-04 GMT+08:00

The CCI team fully noticed the kube-proxy security vulnerability CVE-2020-8558 on July 10. After detailed analysis, it is found that the vulnerability has no impact on users and CCI services, and does not need to be handled.

Vulnerability Details

Kubernetes officially released security vulnerability (CVE-2020-8558) which allows adjacent hosts to access Kubernetes nodes running on the local host.

For example, if a Kubernetes cluster runs a service on a node that listens on 127.0.0.1, because of this bug, the service will be potentially reachable by other hosts on the same LAN as the node, or by hosts on a Layer-2 network. In this way, the port information is obtained. If the example service on the port requires no additional authentication, the service is vulnerable to attacks.

Reference link:

https://github.com/kubernetes/kubernetes/issues/92315

Root Cause

This issue was originally raised by setting net.ipv4.conf.all.route_localnet=1 for kube-proxy. This setting causes the system not to reject traffic that originates on other hosts to the local host.

How Do I Determine Whether a Vulnerability Is Involved?

  • Affected cluster versions are used:
    • kubelet/kube-proxy v1.18.0-1.18.3
    • kubelet/kube-proxy v1.17.0-1.17.6
    • kubelet/kube-proxy v1.16.10 or earlier
  • Your cluster nodes run in an environment where untrusted hosts share the same Layer-2 domain (for example, same LAN) as the cluster nodes.
  • Your cluster allows untrusted pods to run containers with CAP_NET_RAW (Kubernetes clusters allow this capability by default).
  • Your nodes (or pods that use the host network) run localhost services which do not require any further authentication.

For more information, see Am I vulnerable?

Vulnerability Analysis Results

Based on the preceding analysis, CCI is not affected by the vulnerability because:

  • CCI underlying clusters are based on Kubernetes v1.15. However, the kube-proxy component uses self-developed code and does not involve the setting net.ipv4.conf.all.route_localnet=1.
  • The network model of CCI underlying clusters is different from that of common Kubernetes clusters. CCI uses secure containers and is deeply integrated with Huawei Cloud networking services. Your VPC network and the CCI host network are not in the same Layer-2 domain. There is no information leakage risk at the CCI side.
  • By default, net.ipv4.conf.all.route_localnet is set to 0 in the service container kernel. The process bound to localhost cannot access other nodes in the same VPC. There is no information leakage risk at the user side.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback