Advisory

GHSA-3x57-m5p4-rgh4

Also known as: None

Summary

ZendOpenID potential security issue in login mechanism

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-06-07 22:28 UTC
Modified
2024-12-04 05:38 UTC

Affected packages and fixes

zendframework/zendopenid

Packagist · All systems

Affected

  • introduced 2.0.0, fixed 2.0.2 (ecosystem)

Fixed versions

2.0.2

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences