# Use of a Broken or Risky Cryptographic Algorithm (CWE-327)

The product uses a broken or risky cryptographic algorithm or protocol.

**Stack:** Go

- Prevalence: Hoch Häufig ausgenutzt
- Impact: Hoch 3 Regeln mit hohem Schweregrad
- Prevention: Dokumentiert 4 Fix-Beispiele

**OWASP:** Cryptographic Failures (A02:2021-Cryptographic Failures) - #2

## Description

Cryptographic algorithms are the backbone of modern information security. Using algorithms that have known weaknesses, such as MD5 or DES, can make it trivial for attackers to defeat the protection.

## Prevention

Präventionsstrategien für Broken Cryptographic Algorithm basierend auf 1 Shoulder-Erkennungsregeln.

### Go

Replace MD5/SHA1/DES/RC4 with bcrypt, SHA-256, or AES-GCM

## Warning Signs

- [HIGH] Weak cryptographic algorithm detected: ...

## Consequences

- Anwendungsdaten lesen
- Schutzmechanismus umgehen

## Mitigations

- AES-256 für symmetrische Verschlüsselung verwenden
- Für asymmetrische Verschlüsselung RSA-2048+ oder ECDSA verwenden
- Für Hashing SHA-256 oder SHA-3 verwenden

## Detection

- Total rules: 4
- Languages: go, javascript, typescript, python

## Rules by Language

### Go (1 rules)

- **Use of Weak Cryptographic Algorithm** [HIGH]: Uses MD5, SHA1, DES, or RC4 which are cryptographically broken.
  - Remediation: Replace weak cryptographic algorithms with secure alternatives:
- For passwords: use bcrypt, scrypt, or argon2
- For hashing: use SHA-256 or SHA-512
- For encryption: use AES-256-GCM or ChaCha20-Poly1305