Validate WORM/ledger key length loaded from vault #164

Closed
opened 2026-07-27 01:28:29 +00:00 by KofTwentyTwo · 1 comment
KofTwentyTwo commented 2026-07-27 01:28:29 +00:00 (Migrated from github.com)

Found in the 0.E security review (Minor). Only the storage key is length-validated (try_into::<[u8;32]>); WORM/ledger keys loaded from the vault are not. Not exploitable (HMAC accepts any length; keys always minted at 32 bytes) but a truncated stored key would be used silently. Add explicit length validation.

Found in the 0.E security review (Minor). Only the storage key is length-validated (try_into::<[u8;32]>); WORM/ledger keys loaded from the vault are not. Not exploitable (HMAC accepts any length; keys always minted at 32 bytes) but a truncated stored key would be used silently. Add explicit length validation.
KofTwentyTwo commented 2026-07-28 14:06:23 +00:00 (Migrated from github.com)

Superseded by #200 (M6) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.

Superseded by #200 (M6) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/nuncio#164