Hardening: fuzz every untrusted parser and decoder #98

New Issue

hugo · 2026-08-08T08:26:25Z

hugo commented

2026-08-08 08:26:25 +00:00

Objective

Add sustained fuzz/property coverage for wire, LLSD, login/XML, packets/messages, assets, images, meshes, archives, GLTF/Collada, RLV, LSL, and voice signaling.

Deliverables

Seed corpora from every translated malformed/regression fixture.
Assert no panic, hang, arithmetic overflow, path escape, or unbounded allocation; preserve typed errors and limits.
Document reproducible local and CI fuzz commands and retain minimized regressions.

Validation

Focused fuzz budgets pass under sanitizers where supported.
Every discovered defect becomes a direct regression test.
No unsafe parser path lacks explicit invariants and coverage.

Prerequisite

All implementation and program milestones are complete with their fixed parity suites green.

Project constraints

The released implementation is entirely native Rust and must pass the explicit no-CLR/no-bridge artifact audit.
Do not weaken API coverage or semantic parity to satisfy hardening, performance, or packaging goals.
Preserve reproducible evidence, update release documentation, and keep all default/live destructive boundaries explicit.

## Objective Add sustained fuzz/property coverage for wire, LLSD, login/XML, packets/messages, assets, images, meshes, archives, GLTF/Collada, RLV, LSL, and voice signaling. ## Deliverables - Seed corpora from every translated malformed/regression fixture. - Assert no panic, hang, arithmetic overflow, path escape, or unbounded allocation; preserve typed errors and limits. - Document reproducible local and CI fuzz commands and retain minimized regressions. ## Validation - Focused fuzz budgets pass under sanitizers where supported. - Every discovered defect becomes a direct regression test. - No unsafe parser path lacks explicit invariants and coverage. ## Prerequisite All implementation and program milestones are complete with their fixed parity suites green. ## Project constraints - The released implementation is entirely native Rust and must pass the explicit no-CLR/no-bridge artifact audit. - Do not weaken API coverage or semantic parity to satisfy hardening, performance, or packaging goals. - Preserve reproducible evidence, update release documentation, and keep all default/live destructive boundaries explicit.

hugo added this to the 12 - Hardening and release milestone 2026-08-08 08:26:25 +00:00

hugo added the enhancement label 2026-08-08 08:26:25 +00:00

hugo added the wontfix label 2026-08-11 20:05:55 +00:00

hugo commented

2026-08-11 20:06:46 +00:00

fuzzing runs afoul of current model restrictions, so we skip this, even though that is a rather sad result, as it makes the library potentially vulnerable. but that is how openai and anthropic see the world.

hugo closed this issue

2026-08-11 20:06:46 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: hugo/MetaCrate#98