It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token
    pair from the authentication server, permitting indefinite usage in the case of permission revocation. An
    attacker on an already compromised resource could use this flaw to grant himself continued permissions and
    possibly conduct further attacks. (CVE-2017-12160)

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2017:2905 advisory.

    Red Hat Single Sign-On is a standalone server, based on the Keycloak project, that provides authentication     and standards-based single sign-on capabilities for web and mobile applications.

    This release of Red Hat Single Sign-On 7.1.3 serves as a replacement for Red Hat Single Sign-On 7.1.2, and     includes several bug fixes and enhancements. For further information, refer to the Release Notes linked to     in the References section.

    Security Fix(es):

    * 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. (CVE-2017-12158)

    * 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. (CVE-2017-12159)

    * It was found that libpam4j did not properly validate user accounts when authenticating. A user with a     valid password for a disabled account would be able to bypass security restrictions and possibly access     sensitive information. (CVE-2017-12197)

    * It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh     token pair from the authentication server, permitting indefinite usage in the case of permission     revocation. An attacker on an already compromised resource could use this flaw to grant himself continued     permissions and possibly conduct further attacks. (CVE-2017-12160)

    Red Hat would like to thank Mykhailo Stadnyk (Playtech) for reporting CVE-2017-12158; Prapti Mittal for     reporting CVE-2017-12159; and Bart Toersche (Simacan) for reporting CVE-2017-12160. The CVE-2017-12197     issue was discovered by Christian Heimes (Red Hat).

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update for rh-sso7-keycloak is now available for Red Hat Single Sign-On 7.1 for RHEL 6.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat Single Sign-On is a standalone server, based on the Keycloak project, that provides authentication and standards-based single sign-on capabilities for web and mobile applications.

This release of Red Hat Single Sign-On 7.1.3 serves as a replacement for Red Hat Single Sign-On 7.1.2, and includes several bug fixes and enhancements. For further information, refer to the Release Notes linked to in the References section.

Security Fix(es) :

* 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. (CVE-2017-12158)

* 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. (CVE-2017-12159)

* It was found that libpam4j did not properly validate user accounts when authenticating. A user with a valid password for a disabled account would be able to bypass security restrictions and possibly access sensitive information. (CVE-2017-12197)

* It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks. (CVE-2017-12160)

Red Hat would like to thank Mykhailo Stadnyk (Playtech) for reporting CVE-2017-12158; Prapti Mittal for reporting CVE-2017-12159; and Bart Toersche (Simacan) for reporting CVE-2017-12160. The CVE-2017-12197 issue was discovered by Christian Heimes (Red Hat).

ID	Name	Product	Family	Severity
434030	SCA: security update for org.keycloak:keycloak-parent (GHSA-qc72-gfvw-76h7)	Tenable Cloud Security	SCA Checks	high
434030	SCA: security update for org.keycloak:keycloak-parent (GHSA-qc72-gfvw-76h7)	Tenable Self-Hosted Container Security	SCA Checks	high
103957	RHEL 7 : rh-sso7-keycloak (RHSA-2017:2905)	Nessus	Red Hat Local Security Checks	high
103956	RHEL 6 : rh-sso7-keycloak (RHSA-2017:2904)	Nessus	Red Hat Local Security Checks	high

Detections

Analytics

CVE-2017-12160

high

Tenable Plugins

high

high

high

high