Homepage

@backstage/plugin-proxy-backend@0.6.14

A Backstage backend plugin that helps you set up proxy endpoints in the backend

  • latest version

    0.6.18

  • latest non vulnerable version

    0.6.19-next.1

  • first published

    6 years ago

  • latest version published

    29 days ago

  • licenses detected

  • View plugin-proxy-backend package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @backstage/plugin-proxy-backend package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Directory Traversal

    @backstage/plugin-proxy-backend is an A Backstage backend plugin that helps you set up proxy endpoints in the backend

    Affected versions of this package are vulnerable to Directory Traversal via the proxy request path handling in router.ts when an attacker sends a request containing .. path traversal segments (including URL-encoded or backslash variants), allowing them to bypass intended routing restrictions and reach upstream services or internal endpoints that should not be accessible through the proxy. The fix introduces a middleware that decodes and normalises the request path, rejecting any path that contains .. segments before the request is forwarded.

    How to fix Directory Traversal?

    Upgrade @backstage/plugin-proxy-backend to version 0.6.17 or higher.

    <0.6.17
    • M
    Incorrect Authorization

    @backstage/plugin-proxy-backend is an A Backstage backend plugin that helps you set up proxy endpoints in the backend

    Affected versions of this package are vulnerable to Incorrect Authorization via inconsistent application of route credentials in the proxy router (plugins/proxy-backend/src/service/router.ts). The buildMiddleware function registers the dangerously-allow-unauthenticated auth policy on the HTTP router only when that specific route is configured with that policy, but the policy registration is decoupled from the per-request credential enforcement. As a result, a credential-protected proxy route nested below a path already registered as dangerously-allow-unauthenticated inherits the unauthenticated policy, allowing an unauthenticated attacker to reach the protected route without supplying valid credentials. The fix introduces a dedicated readCredentialsPolicy helper and moves auth-policy registration out of buildMiddleware so that each route's credentials setting is applied consistently at the router level.

    How to fix Incorrect Authorization?

    Upgrade @backstage/plugin-proxy-backend to version 0.6.18 or higher.

    >=0.5.0 <0.6.18
    Go back to all versions of this package