cms: Reject AES-256-CBC IV with invalid length

F-NITRO-IVLEN-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

aws/aws-nitro-enclaves-sdk-c #167Security PRaws/aws-nitro-enclaves-sdk-c

cms: Reject AES-256-CBC IV with invalid length

merged

details

Finding IDs: F-NITRO-IVLEN-001
Status: merged
Reported date: 30 Mar 2026
Rationale: rejects malformed CMS AES-256-CBC IV lengths before decryption so short IV buffers cannot reach EVP_DecryptInit_ex unchecked.
PR opened by: @mariusknaust
PR state observed: closed; GitHub merged: true; 2026-09-24
PR observation basis: Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed.
Contribution boundary: Report-associated upstream work; @1seal code authorship is not claimed. Credit, where recorded, is a separate fact.

F-NITRO-IVLEN-001: Memory safety. A short IV buffer reaches a cryptographic out-of-bounds read. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-NITRO-IVLEN-001

Security area (1seal assessment): Memory safety. Rejecting a short AES IV prevents the decrypt initializer from reading beyond the supplied buffer. Reviewed 21 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.