CodeVetter · Repo Unpack · Risk map
fastify/fastify
The principal trust boundaries are request bytes, forwarding headers, application-supplied schemas, and plugin code. The source includes explicit defenses and warnings at several of these boundaries. Shutdown and hijacked responses require coordinated resource cleanup across modules. These are source observations and labeled hypotheses, not confirmed vulnerabilities; no whole-repository absence or exploitability is claimed.
- Schemas are a code-execution trust boundary: documentation warns that validation and serialization use new Function and must not accept user-provided schemas.
- The guide warns against database access during initial async validation because of denial-of-service exposure, recommending preHandler instead.
- External header-schema references retain original case and cannot safely be globally normalized; compilation detects them and emits FSTSEC002.
- Async validator data is treated as pass/fail rather than unwrapped as error/value, explicitly preventing payload fields from replacing request parts or injecting validation errors.
- Body buffering checks both decoded received length and reported encoded length, with separate declared Content-Length verification.
- JSON parsing delegates prototype and constructor handling to secure-json-parse; tests demonstrate that the ignore option permits observable prototype effects through Object.assign.
- Forwarded host and protocol are consumed only when proxyFn trusts the direct socket peer, making trustProxy policy security-sensitive.
- Default error serialization includes error.message, and failed serialization constructs a fallback using both serializer and original error messages.
- Hypothesis: timeout and hijack changes have broad cleanup risk because routeHandler stores AbortController/timer/socket metadata and Reply.hijack removes associated listeners and metadata. (inferred)
- Alternative-runtime unit CI uses continue-on-error, so its configured failures do not provide the same gating signal as an ordinary mandatory job.
- Package-manager CI downloads and pipes a Yarn installer into bash; CITGM derives plugin checkout coordinates from npm registry metadata and runs external package tests.