Single Sign On
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:single_sign_on:7.1:*:*:*:*:*:*:*
part: a version: 7.1 update: *
| Vendor | Redhat (e942785a-ca89-506e-bd99-50782639cde3) |
|---|---|
| Product | Single Sign On (1e613277-631e-5fab-8ccf-23a2cf2a0e98) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-2585 |
vulnerable | 2026-06-08 05:09:24.693102 |
Details available
Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.
Published: 2018-03-12T15:00:00.000Z
Updated: 2024-09-16T22:56:17.924Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-12159 |
vulnerable | 2026-06-08 05:08:45.419266 |
Details available
It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.
Published: 2017-10-26T17:00:00.000Z
Updated: 2024-09-16T21:02:35.248Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-12158 |
vulnerable | 2026-06-08 05:08:45.417825 |
Details available
It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations. An attacker could use this flaw against an authenticated user to attain reflected XSS via a malicious server.
Published: 2017-10-26T17:00:00.000Z
Updated: 2024-09-16T23:36:41.599Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-8629 |
vulnerable | 2026-06-08 05:08:14.506807 |
Details available
Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.
Published: 2018-03-12T15:00:00.000Z
Updated: 2024-09-16T17:52:54.232Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.