界: Security Features

软件安全不是安全软件。此处我们关注的主题包括身份验证、Access Control、机密性、加密和权限管理。

Kubernetes Misconfiguration: Service Account Token Automounted

YAML

Abstract

未禁用 API 凭据的自动挂载。

Explanation

除非另有规定，否则任何新创建的 Pod 都会自动分配一个 default 服务帐户。对于每个服务帐户，会自动生成一个 API 访问令牌，并在挂载的目录中提供该令牌。攻击者可以利用任何受损 Container 中的访问令牌来访问保护不充分和安全敏感的服务 API。

由于未定义 automountServiceAccountToken 或默认服务帐户的配置包含 automountServiceAccountToken: true 设置，因此未禁用 Pod 的默认服务帐户的 API 凭据自动挂载。

示例 1：如果未定义 automountServiceAccountToken，或如本例中所示将其设置为 true，则会自动挂载 Pod 的 default 服务帐户的 API 凭据。


apiVersion: v1
kind: ServiceAccount
metadata:
  name: default
  namespace: demo-namespace
automountServiceAccountToken: true
...

示例 2：自动挂载 Pod 的 API 凭据，因为 default 服务帐户中包含 automountServiceAccountToken: true 设置，如本例中所示。


apiVersion: v1
kind: Pod
  ...
spec:
  automountServiceAccountToken: true
  ...

References

[1] Configure Service Accounts for Pods The Kubernetes Authors

[2] How to _not_ create a service account? kubernetes, GitHub repository

[3] Workload Resources The Kubernetes Authors

[4] Standards Mapping - CIS Kubernetes Benchmark Recommendation 5.1.5, Recommendation 5.1.6

[5] Standards Mapping - Common Weakness Enumeration CWE ID 749

[6] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000213, CCI-000804, CCI-001082, CCI-001084, CCI-002165

[7] Standards Mapping - FIPS200 AC

[8] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

[9] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-3 Access Enforcement (P1), IA-8 Identification and Authentication (Non-Organizational Users) (P1), SC-2 Application Partitioning (P1), SC-3 Security Function Isolation (P1)

[10] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-3 Access Enforcement, IA-8 Identification and Authentication (Non-Organizational Users), SC-2 Separation of System and User Functionality, SC-3 Security Function Isolation

[11] Standards Mapping - OWASP API 2023 API8 Security Misconfiguration

[12] Standards Mapping - OWASP Application Security Verification Standard 4.0 14.5.1 Validate HTTP Request Header Requirements (L1 L2 L3)

[13] Standards Mapping - OWASP Mobile 2014 M5 Poor Authorization and Authentication

[14] Standards Mapping - OWASP Top 10 2004 A2 Broken Access Control

[15] Standards Mapping - OWASP Top 10 2010 A8 Failure to Restrict URL Access

[16] Standards Mapping - OWASP Top 10 2013 A7 Missing Function Level Access Control

[17] Standards Mapping - OWASP Top 10 2017 A5 Broken Access Control

[18] Standards Mapping - OWASP Top 10 2021 A01 Broken Access Control

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 7.2

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 7.2

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.8

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.10

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.8

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.8

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.8

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4

[28] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control, Control Objective C.2.3 - Web Software Access Controls

[31] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 862

[32] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3480.1 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3360 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3470.1 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3470.1 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3470.1 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3470.1 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3470.1 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II, APSC-DV-001870 CAT II, APSC-DV-002150 CAT II, APSC-DV-002360 CAT II

[54] Standards Mapping - Web Application Security Consortium Version 2.00 Insufficient Authorization (WASC-02)

[55] Standards Mapping - Web Application Security Consortium 24 + 2 Insufficient Authorization

desc.structural.yaml.kubernetes_misconfiguration_service_account_token_automounted.base