Cyber Resilience

CVE-2023-51701

Fastify Reply-From ≤ 9.6.0

Published
08 January 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0048 39th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2023-51701 is a medium-severity HTTP Request/Response Smuggling (CWE-444) vulnerability in Fastify Reply-From. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-7 (Boundary Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

fastify-reply-from is a Fastify plugin to forward the current HTTP request to another server. 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…

more

security checks. This vulnerability has been patched in '@fastify/reply-from` version 9.6.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33805Same product: Fastify Reply-From
CVE-2025-66415Same product: Fastify Reply-From
CVE-2026-15631Same vendor: Fastify
CVE-2026-15074Same vendor: Fastify
CVE-2026-22031Same vendor: Fastify
CVE-2023-31999Same vendor: Fastify
CVE-2026-6410Same vendor: Fastify
CVE-2026-6414Same vendor: Fastify
CVE-2023-27495Same vendor: Fastify
CVE-2026-40562Shared CWE-444

Affected Assets

fastify
reply-from
≤ 9.6.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.1.3
  • V4.2.4
  • V1.5.3
  • V4.1.1

Mitigating Controls (NIST 800-53 r5) AI

Boundary protection at external interfaces can enforce consistent HTTP request/response parsing rules between intermediaries and endpoints.

Validating HTTP inputs at the intermediary prevents malformed messages from being interpreted inconsistently downstream.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Configuration management can enforce uniform HTTP parsing rules across intermediaries, directly mitigating inconsistent interpretation.

DE.CM-01 partial match
prevents

Network monitoring can detect smuggling attempts via anomalous HTTP traffic or logs, while eliminating the inconsistency directly aids detection of such events.

PR.IR-01 partial match
prevents

Network protections can enforce consistent HTTP proxy/firewall behavior to block smuggling, and removing the weakness helps prevent unauthorized access via request smuggling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect HTTP request smuggling vulnerabilities in intermediary components.

degrades

Network security controls can enforce consistent HTTP parsing and proxy behavior that mitigates request smuggling.

degrades

Secure network services include hardening proxies and gateways against inconsistent HTTP interpretation.

prevents

Secure SDLC practices require threat modeling and testing for HTTP parsing inconsistencies in intermediaries.

prevents

Application security requirements can mandate strict HTTP message validation and canonicalization.

prevents

Secure architecture principles include consistent protocol handling and defense-in-depth for proxies.

References