phpCAS authentication library < 1.6.0 - Service Hostname Discovery Exploitation

8.0
Improper Validation of Specified Type of Input
CVE CVE-2022-39369
CVSS 8.0 (High)
Publicly Published November 1, 2022
Last Updated August 7, 2023
Researcher Filip Hejsek

Description

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.

References

Share

Vulnerability Details for Authorizer

Software Type Plugin
Software Slug authorizer (view on wordpress.org)
Patched? Yes
Remediation Update to version 1.6.0, or a newer patched version
Affected Version
  • < 1.6.0
Patched Version
  • 1.6.0

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation