Back to bug 2180886
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Pedro Sampaio | 2023-03-22 14:20:28 UTC | CC | security-response-team | |
| Pedro Sampaio | 2023-03-22 14:25:42 UTC | Blocks | 2180888 | |
| Patrick Del Bello | 2023-03-22 20:09:58 UTC | CC | anstephe, avibelli, bgeorges, clement.escoffier, dandread, dkreling, gsmet, hamadhan, jmartisk, lthon, max.andersen, pgallagh, pjindal, probinso, rruss, rsvoboda, sbiarozk, sdouglas | |
| Patrick Del Bello | 2023-03-22 20:14:59 UTC | Priority | high | low |
| Doc Text | Quarkus OIDC can leak both ID and access tokens in the authorization code flow when insecure HTTP protocol is used which can allow attackers to access sensitive user data, directly from the ID token or by using the access token to access user data from OIDC provider services. | |||
| Severity | high | low | ||
| Patrick Del Bello | 2023-03-22 20:15:34 UTC | Alias | CVE-2023-1584 | |
| Summary | EMBARGOED quarkus-oidc: ID and access tokens leak via the authorization code flow | EMBARGOED CVE-2023-1584 quarkus-oidc: ID and access tokens leak via the authorization code flow | ||
| Patrick Del Bello | 2023-03-22 20:22:46 UTC | Doc Text | Quarkus OIDC can leak both ID and access tokens in the authorization code flow when insecure HTTP protocol is used which can allow attackers to access sensitive user data, directly from the ID token or by using the access token to access user data from OIDC provider services. | Quarkus OIDC can leak both ID and access tokens in the authorization code flow when insecure HTTP protocol is used which can allow attackers to access sensitive user data, directly from the ID token or by using the access token to access user data from OIDC provider services. Passwords are not stored in access tokens. |
| Group | security, qe_staff | |||
| Summary | EMBARGOED CVE-2023-1584 quarkus-oidc: ID and access tokens leak via the authorization code flow | CVE-2023-1584 quarkus-oidc: ID and access tokens leak via the authorization code flow | ||
| Patrick Del Bello | 2023-03-22 20:24:21 UTC | Doc Text | Quarkus OIDC can leak both ID and access tokens in the authorization code flow when insecure HTTP protocol is used which can allow attackers to access sensitive user data, directly from the ID token or by using the access token to access user data from OIDC provider services. Passwords are not stored in access tokens. | A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when insecure HTTP protocol is used which can allow attackers to access sensitive user data, directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens. |
| Paige Jung | 2023-03-22 21:25:55 UTC | Doc Text | A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when insecure HTTP protocol is used which can allow attackers to access sensitive user data, directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens. | A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens. |
| errata-xmlrpc | 2023-06-29 11:09:53 UTC | Link ID | Red Hat Product Errata RHSA-2023:3809 | |
| Product Security DevOps Team | 2023-06-29 16:16:14 UTC | Resolution | --- | ERRATA |
| Status | NEW | CLOSED | ||
| Last Closed | 2023-06-29 16:16:14 UTC |
Back to bug 2180886