org.keycloak:keycloak-saml-core@26.7.2

  • latest version

    26.7.2

  • first published

    11 years ago

  • latest version published

    12 days ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the org.keycloak:keycloak-saml-core 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
    • H
    Replay Attack

    org.keycloak:keycloak-saml-core is an Identity and Access Management plugin for Keycloak.

    Affected versions of this package are vulnerable to Replay Attack through IdP-initiated broker logins in the services/src/main/java/org/keycloak/broker/saml component. An attacker can hijack a user session and gain unauthorized access by resending a captured, valid SAML assertion that contains a OneTimeUse condition. When Keycloak accepts the assertion without tracking whether that assertion ID was already used, the same unused response can be replayed multiple times against the broker flow. This affects deployments using Keycloak as a SAML identity broker with IdP-initiated login enabled.

    How to fix Replay Attack?

    A fix was pushed into the master branch but not yet published.

    [0,)
    • M
    Improper Handling of Extra Parameters

    org.keycloak:keycloak-saml-core is an Identity and Access Management plugin for Keycloak.

    Affected versions of this package are vulnerable to Improper Handling of Extra Parameters through the generateRedirectUri logic in org.keycloak.saml.BaseSAML2BindingBuilder. An attacker can cause a user’s SAML login response to be appended to attacker-controlled query parameters by sending a crafted SAML HTTP-Redirect request that targets a client with a wildcard redirect URL. When the user authenticates, Keycloak preserves the attacker-supplied parameters alongside SAMLResponse or SAMLRequest and RelayState, which can make a service provider process the wrong values. This can log the user into the attacker’s chosen account or otherwise misassociate the authentication response with the wrong session.

    How to fix Improper Handling of Extra Parameters?

    A fix was pushed into the master branch but not yet published.

    [0,)