GHSA-pfrg-qg4f-grmv: 
Rust vulnerability analysis and mitigation

Impact

The graphql() and graphql_sync() functions of juniper_hyper read the whole body of a POST request into memory before they parse the body. The functions had no limit on the size of the body. A client could thus send a large body and exhaust the memory of the server. The request needs no authentication. Bodies of the application/json and application/graphql content types were affected.

Patches

juniper_hyper 0.10.1 reads at most 2 MiB of a request body by default. The functions respond with 413 Payload Too Large to larger bodies. A juniper_hyper::BodyLimit in the extensions of a request changes the limit for the request.

Workarounds

Check the Content-Length header before the call of graphql() or graphql_sync(). Reject requests with a large value or without the header.

References

• Changelog of juniper_hyper 0.10.1
• Changes from 0.10.0 to 0.10.1