Skip to content

Micronaut Security 4.18.2

Choose a tag to compare

@sdelamo sdelamo released this 11 Nov 08:18
· 1 commit to 4.18.x since this release

Security fixes 🔒

Micronaut Security 4.18.2 fixes the following security advisories. We recommend that all users upgrade.

Critical

  • GHSA-225x-m3g7-h3fc: Intercept URL map auth bypass via an encoded slash or blank path variable. Patterns are now matched against the routed path.
  • GHSA-5gmg-jhq8-8f46: Auth bypass when a @Secured expression evaluates to null. Such requests are now rejected.
  • GHSA-9p96-xfm5-fhrr: Intercept URL map root pattern bypassed when a context path is set.

High

  • GHSA-qg4x-g29m-8972: Auth bypass outside idtoken mode via ID tokens issued to other clients. The OpenID provider JWKS is now restricted to ID token validation.
  • GHSA-jmhh-jwqx-v9xr: The token endpoint, JWKS and other identity provider clients followed redirects (SSRF). They no longer follow redirects.

Medium

  • GHSA-5jg2-867c-v33w: CSRF bypass in session mode via a planted CSRF cookie. The session CSRF token is now authoritative.
  • GHSA-jqmr-rmh4-7vwq: CsrfFilter returned 500 on a malformed form body, allowing log injection. Malformed bodies are now rejected.
  • GHSA-fp7x-m8rj-c99q: Open redirect in prior-to-login via a request path with leading slashes. The redirect is now restricted to local paths.
  • GHSA-48pg-wgcc-jr7h: The OAuth 2.0 client redeemed stolen codes using the redirect_uri from the state. The token request redirect_uri is now built from the callback route.
  • GHSA-r5p7-rhcj-jh75: IdTokenClaimsValidator accepted ID tokens for disabled OAuth 2.0 clients.
  • GHSA-7mp3-v9m3-xj9c: The JWKS was not bound to the issuer, so one provider could sign tokens as another.
  • GHSA-qr8w-hxv9-92gh: The JWT issuer check accepted any suffix of the expected issuer, even an empty one. Issuer matching is now exact.
  • GHSA-2hvh-qgrg-9x4v: The UserInfo token validator let one provider impersonate another provider's users. Authentications are now bound to the answering provider.
  • GHSA-53fg-fcg3-rhpg: TokenAuthenticationFetcher leaked accepted JWTs to every UserInfo endpoint. Token validators are now consulted sequentially and stop at the first match.
  • GHSA-jw86-wc3g-4qw2: DefaultOpenIdAuthenticationMapper mapped the same sub at two providers to one user. Usernames are now qualified with the provider when several clients exist.
  • GHSA-3885-wfpm-p3p3: LDAP group names were split at commas, granting the roles of other groups.
  • GHSA-q334-qw3j-c38x: LDAP username enumeration via the "User Not Found" reason and bind timing.
  • GHSA-cjfm-j2vw-r8g8: IpPatternsRule treated dots as wildcards, so the documented 192.168.1.* range also admitted 192.168.10.x.
  • GHSA-hj4f-f856-x9p6: SignedRefreshTokenGenerator logged introspected tokens at WARN.
  • GHSA-rw57-vf5m-cw29: Access tokens were logged at DEBUG via the toString of AccessTokenGeneratedEvent and other token-carrying events. Tokens are now redacted.

Low

  • GHSA-35xw-qhv4-3j97: IssuerClaimValidator let one provider spoof another's issuer via discovery. The ID token issuer is now validated against the configured OpenID issuer.
  • GHSA-4cpp-jg7m-qmrg: JWKS signature validation ignored the configured key type (since 3.11.0).
  • GHSA-3342-vfw6-p36c: A failed JWKS fetch was retried for every bearer token, with no back-off.
  • GHSA-8q27-vgx7-m7rx: Memory leak in NimbusJsonWebTokenSignatureValidator via an unverified alg header. The unbounded cache has been removed.
  • GHSA-7mr8-3phg-5p2c: The end session URL was expanded as a URI template, so a provider could cause an OOM.
  • GHSA-gc9r-29h7-j22g: OktaEndSessionEndpoint leaked a gateway's bearer token as id_token_hint.
  • GHSA-mch3-j785-25rx: Username enumeration because single-valued keys such as micronaut.security.ldap.enabled were bound as an LDAP configuration with no server.

Full Changelog: v4.18.1...v4.18.2