Homepage

@backstage/plugin-auth-backend@0.27.1-next.1 vulnerabilities

A Backstage backend plugin that handles authentication

  • latest version

    0.27.1

  • latest non vulnerable version

    0.27.1

  • first published

    5 years ago

  • latest version published

    2 days ago

  • licenses detected

  • View plugin-auth-backend package health on Snyk Advisor  (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-auth-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
    Open Redirect

    @backstage/plugin-auth-backend is an A Backstage backend plugin that handles authentication

    Affected versions of this package are vulnerable to Open Redirect via the OAuth redirect URI validation bypass. An attacker can intercept authorization codes by crafting a redirect URI that bypasses the allowlist and leads to an attacker-controlled host, provided a victim approves the OAuth consent request. This is only exploitable if experimental Dynamic Client Registration or Client ID Metadata Documents features are explicitly enabled.

    Note:

    This issue affects experimental Dynamic Client Registration and Client ID Metadata Documents features with configured allowedRedirectUriPatterns.

    How to fix Open Redirect?

    Upgrade @backstage/plugin-auth-backend to version 0.27.1 or higher.

    <0.27.1
    • M
    Server-side Request Forgery (SSRF)

    @backstage/plugin-auth-backend is an A Backstage backend plugin that handles authentication

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the CIMD metadata fetch when the auth.experimentalClientIdMetadataDocuments.enabled setting is enabled. An attacker can cause the server to make requests to unintended internal resources by leveraging HTTP redirects after the initial hostname validation. This is only exploitable if the experimental feature is explicitly enabled and allowedClientIdPatterns is not restricted to trusted domains.

    Note:

    The practical impact is limited. The attacker cannot read the response body from the internal request, cannot control request headers or method, and the feature must be explicitly enabled via an experimental flag that is off by default.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade @backstage/plugin-auth-backend to version 0.27.1 or higher.

    >=0.27.0 <0.27.1
    Go back to all versions of this package