# Cleartext Transmission of Sensitive Information (CWE-319) The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. **Stack:** Kubernetes - Prevalence: 高 頻繁に悪用される - Impact: ハイ 5 件の重大度ハイのルール - Prevention: 文書化済み 6 件の修正例 **OWASP:** Cryptographic Failures (A02:2021-Cryptographic Failures) - #2 ## Description Many communication channels can be sniffed by attackers during data transmission. When sensitive data is transmitted without encryption, an attacker can intercept and read this information. Secure channels like TLS should be used to protect sensitive data in transit. ## Prevention ### Kubernetes Configure TLS on Ingress resources to encrypt traffic in transit Remove insecure-skip-tls-verify and use proper certificate verification with CA certificates ## Warning Signs - [HIGH] Ingress exposes HTTP traffic without TLS encryption - [HIGH] Kubernetes Ingress resources without TLS configuration - [HIGH] TLS certificate verification disabled (vulnerable to MITM attacks) - [HIGH] when TLS certificate verification is disabled in Kubernetes configurations ## Consequences - アプリケーションデータの読み取り - 保護メカニズムの回避 ## Mitigations - 機密データはすべて送信前に暗号化する - 機密データを送信するすべての接続で TLS/SSL を使用する - モバイルアプリでは証明書ピン留めを実装する ## Detection - Total rules: 6 - Languages: go, kubernetes, yaml, python ## Rules by Language ### Yaml (2 rules) - **Ingress Missing TLS Configuration** [HIGH]: Detects Kubernetes Ingress resources without TLS configuration. - Remediation: Configure TLS for Ingress resources. ```yaml spec: tls: - hosts: [example.com] secretName: example-tls ``` Learn more: https://shoulder.dev/learn/kubernetes/cwe-319/ingress-missing-tls - **Insecure TLS Verification Disabled** [HIGH]: Detects when TLS certificate verification is disabled in Kubernetes configurations. - Remediation: Remove the insecure TLS skip setting and use proper certificate verification. ### Kubernetes (1 rules) - **Ingress Missing TLS Configuration** [HIGH]: Detects Kubernetes Ingress resources without TLS configuration. - Remediation: Configure TLS for Ingress resources. ```yaml spec: tls: - hosts: [example.com] secretName: example-tls ``` Learn more: https://shoulder.dev/learn/kubernetes/cwe-319/ingress-missing-tls