Skip to content

@fastify/reply-from JSON Content-Type parsing confusion

Moderate severity GitHub Reviewed Published Jan 8, 2024 in fastify/fastify-reply-from • Updated Jan 8, 2024

Package

npm @fastify/reply-from (npm)

Affected versions

< 9.6.0

Patched versions

9.6.0

Description

Impact

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.

Patches

@fastify/reply-from v9.6.0 include the fix.

Workarounds

There are no known workarounds.

References

Hackerone Report: https://hackerone.com/reports/2295770.

References

@mcollina mcollina published to fastify/fastify-reply-from Jan 8, 2024
Published by the National Vulnerability Database Jan 8, 2024
Published to the GitHub Advisory Database Jan 8, 2024
Reviewed Jan 8, 2024
Last updated Jan 8, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.048%
(19th percentile)

Weaknesses

CVE ID

CVE-2023-51701

GHSA ID

GHSA-v2v2-hph8-q5xp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.