همهٔ گزارش‌ها
زیاد

@fastify/static: @fastify/static: Information disclosure via route guard bypass

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-18427

احتمال بهره‌برداری در ۳۰ روز آینده: 0.66%

FIRST EPSS · ۱۴۰۵/۰۸/۳۰

شرح آسیب‌پذیری

@fastify/static before version 10.1.3 contains an incomplete fix for a previous route guard bypass. The static file handler rejected only parent directory segments, but it did not canonicalize dot segments, duplicate slashes, encoded dots, or backslashes before route matching and before delegating to the send layer. As a result, an unauthenticated attacker could request a file protected by a route based guard using a non canonical path form that misses the guarded route yet resolves back onto the protected file, disclosing its contents. Applications that protect a subtree of the static root with a route based guard are affected, while applications relying on the allowedPath option are not. This is fixed in @fastify/static 10.1.3, which canonicalizes the pathname, including rejecting backslashes, on the path used for routing and serving.

A flaw was found in @fastify/static. An unauthenticated attacker can bypass route-based guards by using non-canonical path segments in a request. This allows the attacker to access and disclose the contents of files that should be protected by these guards. The vulnerability stems from the static file handler's failure to properly canonicalize various path forms, such as dot segments, duplicate slashes, encoded dots, or backslashes, before matching routes and serving files.