189922 matches found
ECHO-7E4D-4229-7370
Bulletin has no description...
ECHO-1EC0-58D1-CB3D Keycloak's GHSA advisory (GHSA-gv3v-2cpp-3pmq) lists the affected package/range as org.keycloak:keycloak-quarkus-server < 26.5.6 with no lower bound, so by version string alone 25.0.6 is nominally in range. The actual vulnerable mechanism is the HTTP access log feature (config.HttpAccessLogOptions, HttpAccessLogPropertyMappers) added by the fix commit's PR to mask Authorization/Cookie headers in a verbose access-log pattern. That feature does not exist in 25.0.6 at all — confirmed via a full source search (no HttpAccessLogOptions.java, HttpAccessLogPropertyMappers.java, or any http-access-log config option anywhere in quarkus/config-api or quarkus/runtime). There is no access-log-pattern mechanism in this version capable of the described header disclosure.
Bulletin has no description...
ECHO-2AAB-293D-53AF
Bulletin has no description...
ECHO-1969-C688-A45C Keycloak's GHSA advisory (GHSA-rr5q-3xwr-f323) lists the affected range as < 26.6.3 with no lower bound, so by version string alone 25.0.6 is nominally in range. The actual vulnerability requires a generic parameter-length-limiting mechanism (OIDCProviderConfig's max-length-per-parameter config, TokenEndpoint's checkParameters() gate) that silently drops any oversized request parameter, including subject_token — the fix exempts token-shaped parameters from that drop via a new getTokenParameterNames() method. That length-limiting framework does not exist anywhere in 25.0.6 (same finding as CVE-2026-4634, investigated separately) — confirmed via source search, no getMaxLengthForTheParameter/checkParameters/length-cap mechanism exists on any OIDC grant-type endpoint. With no mechanism to silently drop an oversized subject_token, the described fallback to client-credentials cannot occur.
Bulletin has no description...
ECHO-73AB-600D-62BE Caught by Cursor Bugbot review on PR #19827: the real vulnerability (GHSA-7xf9-4jfc-wgm4) is specific to Fine-Grained Admin Permissions V2's RealmPermissionsV2 treating manage-clients as equivalent to managing the special "admin-permissions" client, which then grants realm-wide admin power. RealmPermissionsV2 and the admin-permissions client concept do not exist in 25.0.6 — its older RealmPermissions.canManageAuthorizationDefault() has no per-ResourceServer parameter at all (it's a single, undifferentiated realm-wide check), so there is no "is this the special admin-permissions client" distinction for a narrow, upstream-faithful fix to attach to. An earlier patch here unconditionally removed MANAGE_CLIENTS from that check to close the described escalation, but that changes intended authorization behavior for every regular client's authorization management, not just a vulnerable path (upstream's real fix leaves the MANAGE_CLIENTS grant intact for non-admin-permissions clients) — reverted.
Bulletin has no description...
ECHO-FEA2-5EA1-2849
Bulletin has no description...
ECHO-7EDB-23C5-02EC
Bulletin has no description...
ECHO-F035-45D7-D0F3
Bulletin has no description...
ECHO-8C0B-1F50-633C
Bulletin has no description...
ECHO-C70D-0DFC-E7D7
Bulletin has no description...
ECHO-C80E-9875-82A0
Bulletin has no description...
ECHO-A380-E585-5861
Bulletin has no description...
ECHO-9E12-01FD-007B
Bulletin has no description...
ECHO-0030-65EC-F55D
Bulletin has no description...
ECHO-8712-B79A-9ACD
Bulletin has no description...
ECHO-B87A-6495-4598 Flagged by review on PR #19827: this ID needs a documented disposition here, not silent removal, since the raw scanner (matching on [email protected]'s version string alone) will otherwise keep reporting it as an open finding forever. Upstream's fix (GHSA-gvgg-2r3r-53x7) closes a path where OrganizationMemberResource trusted a client-session note to determine organization membership, letting a crafted note forge an org claim. 25.0.6's OrganizationMembershipMapper does not have that trust path at all — it always re-verifies membership directly against the organization store (provider.getByMember(user)) rather than trusting anything client- or session-supplied. With no client-session-note-based membership check present, the described forgery has no mechanism to exploit here.
Bulletin has no description...
MINI-XP63-3C6H-36JQ
Bulletin has no description...
MINI-M826-28QR-7WCW
Bulletin has no description...