Compliance Impact

This vulnerability allows attackers to bypass route-based middleware or guards that protect files served by @fastify/static by exploiting a mismatch in path separator decoding. Such unauthorized access to protected files could lead to exposure of sensitive data.

By potentially exposing protected files or data, this vulnerability may impact compliance with standards and regulations like GDPR or HIPAA, which require strict access controls and protection of sensitive information.

However, the provided information does not explicitly describe the compliance impact or specific regulatory consequences.

Useful 0 Not Useful 0

Executive Summary

The vulnerability exists in @fastify/static versions 8.0.0 through 9.1.0 where percent-encoded path separators (%2F) are decoded before filesystem resolution, but Fastify's router treats these encoded separators as literal characters. This inconsistency allows attackers to bypass route-based middleware or guards that are intended to protect files served by @fastify/static.

For example, an attacker can circumvent a route guard on a protected path by encoding the path separator in the URL, effectively bypassing security controls.

The issue is fixed in @fastify/static version 9.1.1, and there are no workarounds available.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow attackers to bypass route-based middleware or guards that protect sensitive files served by @fastify/static. As a result, unauthorized users may gain access to protected resources or files that should otherwise be restricted.

Such unauthorized access can lead to exposure of sensitive information or data leakage, potentially compromising the security of your application.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade @fastify/static to version 9.1.1 or later to fix the issue.

There are no workarounds available for this vulnerability.

Useful 0 Not Useful 0