GitHub Advisoryadvisory · Packagist
GHSA-3x57-m5p4-rgh4 ZendOpenID potential security issue in login mechanism
HIGH
Official page ↗
- Ecosystem
- Packagist
- Packages
- zendframework/zendopenid
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Weaknesses
- CWE-287
- Reviewed
- 2024-06-07
Affected packages
• Packagist zendframework/zendopenid: >= 2.0.0, < 2.0.2 → fixed in 2.0.2
Description
Using the Consumer component of ZendOpenId (or Zend_OpenId in ZF1), it is possible to login using an arbitrary OpenID account (without knowing any secret information) by using a malicious OpenID Provider. That means OpenID it is possible to login using arbitrary OpenID Identity (MyOpenID, Google, etc), which are not under the control of our own OpenID Provider. Thus, we are able to impersonate any OpenID Identity against the framework.
Moreover, the Consumer accepts OpenID tokens with arbitrary signed elements. The framework does not check if, for example, both openid.claimed_id and openid.endpoint_url are signed. It is just sufficient to sign one parameter. According to https://openid.net/specs/openid-authentication-2_0.html#positive_assertions, at least op_endpoint, return_to, response_nonce, assoc_handle, and, if present in the response, claimed_id and identity, must be signed.
Related
Weakness · CWE (1)
- CWE-287 Improper Authentication weakness
References
- https://github.com/zendframework/ZendOpenId/commit/16648e1b2acf760d0c67a8c1dd913fed0c0f61f7 web
- https://github.com/zendframework/ZendOpenId/commit/709789c1ca290771730133db4d8b8de2972b36ce web
- https://framework.zend.com/security/advisory/ZF2014-02 web
- https://github.com/FriendsOfPHP/security-advisories/blob/master/zendframework/zendopenid/ZF2014-02.yaml web
- https://github.com/zendframework/ZendOpenId package