The main repo of fastify use fast-content-type-parse to parse request Content-Type, which will trim after split.
The fastify-reply-from have not use this repo to unify the parse of Content-Type, which won't trim.
As a result, a reverse proxy server built with @fastify/reply-from could misinterpret the incoming body by passing an header ContentType: application/json ; charset=utf-8. This can lead to bypass of security checks.
@fastify/reply-from v9.6.0 include the fix.
There are no known workarounds.
Hackerone Report: https://hackerone.com/reports/2295770.
{
"github_reviewed": true,
"github_reviewed_at": "2024-01-08T15:22:40Z",
"nvd_published_at": "2024-01-08T14:15:46Z",
"cwe_ids": [
"CWE-444"
],
"severity": "MODERATE"
}