Skip to content

Unbounded attestation length allows memory‑exhaustion DoS #119

@ameba23

Description

@ameba23

This is a security issue relating to AttestedTlsServer / AttestedTlsClient.

Both server and client read a 4‑byte length prefix and allocate Vec of that size without a cap. A malicious peer can send a huge length and force large allocations. This happens in src/attested_tls.rs:165–172 and src/attested_tls.rs:349–355.

Mitigation would be to cap this at a sensible length - considerably larger than current attestation evidence payloads, but not dangerously high.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions