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 applicationsLearn about Incorrect Authorization vulnerabilities in an interactive lesson.
Start learningUpgrade astro to version 7.2.4 or higher.
astro is an Astro is a modern site builder with web best practices, performance, and DX front-of-mind.
Affected versions of this package are vulnerable to Incorrect Authorization in BaseApp.removeBase, FetchState pathname stripping, and matchRequest in the routing and app base-handling code. An attacker can reach protected routes by sending a request whose pathname extends the configured base with a non-segment suffix, such as /appX/admin, causing routing to resolve the request as /admin while middleware still inspects the unstripped /appX/admin pathname. This lets an unauthenticated remote attacker bypass pathname-based middleware checks and access routes the application intended to protect under a non-root base.
Workarounds
base followed by a path-segment boundary, so paths like /appX/admin, /app2/admin, or /app-/admin are not treated as being under /app and cannot bypass pathname-based middleware authorization.context.url.pathname for authorization when using a non-root base; enforce route access in a way that only permits the exact base path or paths under base/, preventing the router and middleware from disagreeing about whether a request is protected.