Lucene search

K
githubGitHub Advisory DatabaseGHSA-3X57-M5P4-RGH4
HistoryJun 07, 2024 - 10:28 p.m.

ZendOpenID potential security issue in login mechanism

2024-06-0722:28:46
CWE-287
GitHub Advisory Database
github.com
5
security issue
openid
zendopenid
consumer component
arbitrary openid account
malicious openid provider
impersonation
arbitrary signed elements

AI Score

7.2

Confidence

High

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.

Affected configurations

Vulners
Node
zendframeworkzendopenidRange2.0.02.0.2
VendorProductVersionCPE
zendframeworkzendopenid*cpe:2.3:a:zendframework:zendopenid:*:*:*:*:*:*:*:*

AI Score

7.2

Confidence

High