Supply Chain Attack - Kubernetes
Description
Kubernetes dependencies are not pinned to an exact digest, making the docker build unable the verify the integrity of the image and allowing a malicious actor to override the used components with malicious components without leaving a trace.
Impact
Override dependencies or component with malicious content.
Recommendation
Use mechanisms such as git-commits, or artifacts and hashes to verify the data integrity.
Threat
Anonymous attacker from Internet with write access to the provider releases.
Expected Remediation Time
⌚ 15 minutes.
Score
Default score using CVSS 3.1. It may change depending on the context of the src.
Base
- Attack vector: N
- Attack complexity: H
- Privileges required: N
- User interaction: R
- Scope: U
- Confidentiality: N
- Integrity: L
- Availability: N
Temporal
- Exploit code maturity: U
- Remediation level: O
- Report confidence: R
Result
- Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N/E:U/RL:O/RC:R
- Score:
- Base: 3.1
- Temporal: 2.6
- Severity:
- Base: Low
- Temporal: Low
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: N
- Attack complexity: H
- Attack Requirements: N
- Privileges required: N
- User interaction: P
- Confidentiality (VC): N
- Integrity (VI): L
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: U
Result 4.0
- Vector string: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
- Score:
- CVSS-BT: 0.6
- Severity:
- CVSS-BT: Low
Compliant code
All docker dependencies are pinned using secure mechanisms
apiVersion: v1
kind: Pod
metadata:
name:
spec:
containers:
- name:
image: ubuntu@sha256:45b23dee08af5e43a7fea6c4cf9c25ccf269ee113168c19722f87876677c5cb2
Non compliant code
There are docker dependencies not pinned
apiVersion: v1
kind: Pod
metadata:
name:
spec:
containers:
- name:
image: ubuntu
Requirements
Fixes
