Security Resilience

CWE · MITRE source

CWE-329Generation of Predictable IV with CBC Mode

Abstraction: Variant · CVEs in our corpus: 16

The product generates and uses a predictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode, which causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key.

CBC mode eliminates a weakness of Electronic Code Book (ECB) mode by allowing identical plaintext blocks to be encrypted to different ciphertext blocks. This is possible by the XOR-ing of an IV with the initial plaintext block so that every plaintext block in the chain is XOR'd with a different value before encryption. If IVs are reused, then identical plaintexts would be encrypted to identical ciphertexts. However, even if IVs are not identical but are predictable, then they still break the security of CBC mode against Chosen Plaintext Attacks (CPA).

Last updated: 19 November 2026 21:43 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: full · 11 mapping(s) from 4 framework(s): ISO_IEC_27002_2022 7 (full) · 800-53 2 (partial) · 1 (mostly) · ATT&CK 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A04:2025 Cryptographic Failures.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.PS-06
  • SC-13 Cryptographic Protection
  • SA-8 Security and Privacy Engineering Principles
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V11.6.1
Our mappings

NIST 800-53 r5 controls PROPOSED for this weakness (0)

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.
Our mappings

MITRE ATT&CK techniques this weakness enables

Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).

Direction: ← other covers this; → this covers other (F/M/P = full / mostly / partial). gov = governs / implements (a mandate, not coverage).

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2014-3566 7.03.41.00002014-10-15
CVE-2026-45787 6.59.10.00102026-05-28
CVE-2022-46397 5.97.50.00622023-03-28
CVE-2025-59322 5.97.50.00492026-08-12
CVE-2020-5408 5.46.50.01592020-05-14
CVE-2017-3226 4.86.40.00272018-07-24
CVE-2021-27499 4.75.90.00472021-08-02
CVE-2008-5161 4.53.70.18552008-11-19
CVE-2024-49783 4.25.30.00332025-07-08
CVE-2026-863634.15.50.00142026-11-11
CVE-2024-56141 3.95.00.00162026-07-07
CVE-2017-3225 3.74.60.00312018-07-24
CVE-2026-14969 3.44.40.00112026-07-07
CVE-2025-2814 3.34.00.00202025-04-13
CVE-2026-171373.14.00.00092026-11-07
CVE-2022-29054 2.83.30.00172023-02-16