The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade @hono/node-server to version 1.19.18, 2.1.6 or higher.
@hono/node-server is a Node.js Adapter for Hono
Affected versions of this package are vulnerable to Interpretation Conflict via the newRequest function in src/request.ts, which passes the raw request-target directly to the WHATWG URL parser. The WHATWG URL parser treats a backslash in the path as a forward slash and resolves .. segments, so a request for /public\..\admin/secret is normalized to /admin/secret inside the application. A reverse proxy such as nginx, HAProxy, or Envoy follows RFC 3986 and forwards the backslash unchanged, applying its path-based access rules to the original path, meaning the proxy blocks the request on one path while the application processes it on a different, normalized path. An unauthenticated attacker can therefore reach routes that a reverse proxy, load balancer, or WAF is configured to block.
Note: This is only exploitable when the application is deployed behind a front component (reverse proxy, load balancer, or WAF) that makes path-based access decisions and forwards raw backslashes unchanged.