# 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:** Python

- 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

### Python

Use HTTPS for all external requests and enable SSL redirect in frameworks

## Warning Signs

- [HIGH] use of unencrypted HTTP for sensitive operations like API calls,
authentication, payment processing,

## Consequences

- 애플리케이션 데이터 읽기
- 보호 메커니즘 우회

## Mitigations

- 모든 민감한 데이터는 전송 전에 암호화하세요
- 민감한 데이터를 전송하는 모든 연결에 TLS/SSL을 사용하세요
- 모바일 애플리케이션에는 인증서 피닝을 구현하세요

## Detection

- Total rules: 6
- Languages: go, kubernetes, yaml, python

## Rules by Language

### Python (1 rules)

- **HTTP Used Instead of HTTPS** [HIGH]: Detects use of unencrypted HTTP for sensitive operations like API calls,
authentication, payment processing, or data transmission. HTTP traffic is
sent in cleartext and can be intercepted. Always use HTTPS.
  - Remediation: Use HTTPS for all external requests and enable SSL redirect.

```python
import requests

API_URL = "https://api.example.com"

response = requests.get(f"{API_URL}/data", verify=True, timeout=10)

# Django settings.py
SECURE_SSL_REDIRECT = True
SESSION_COOKIE_SECURE = True
```

Learn more: https://shoulder.dev/learn/python/cwe-319/http-not-https