CVE-2022-39369

phpCAS authentication library < 1.6.0 - Service Hostname Discovery Exploitation

2022-11-01 00:00
Filip Hejsek

Strategic Overview

Status
Patched in 1.6.0
Affected Plugin
Authorizer
Affected Version
< 1.6.0
CVSS
8.0High
Weakness type
CWE-1287 · Improper Validation of Specified Type of Input
CVE
CVE-2022-39369
View all Authorizer vulnerabilities

At a glance

CVE-2022-39369 is a high-severity Improper Validation of Specified Type of Input vulnerability in the Authorizer WordPress plugin, affecting versions < 1.6.0. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.6.0; sites on affected versions should update now. Disclosed November 2022, reported by Filip Hejsek.

Vulnerability Overview

The phpCAS library uses HTTP headers to determine the service URL used to validate tickets. This allows an attacker to control the host header and use a valid ticket granted for any authorized service in the same SSO realm (CAS server) to authenticate to the service protected by phpCAS. Depending on the settings of the CAS server service registry in worst case this may be any other service URL (if the allowed URLs are configured to "^(https)://.*") or may be strictly limited to known and authorized services in the same SSO federation if proper URL service validation is applied. This vulnerability may allow an attacker to gain access to a victim's account on a vulnerable CASified service without victim's knowledge, when the victim visits attacker's website while being logged in to the same CAS server. WordPress plugins containing a vulnerable copy of this library may or may not be vulnerable to exploitation.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-1287: Improper Validation of Specified Type of Input

The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.

Remediation

Update to version 1.6.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Authorizer 1.6.0 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C