{"items":[{"id":"NVI-00003198","kind":"vulnerability","title":"ZendOpenID potential security issue in login mechanism","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3x57-m5p4-rgh4"],"plain_summary":"OSV carries this publisher advisory for zendframework/zendopenid. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.0.2 for zendframework/zendopenid. Confirm the publisher’s latest guidance.","source_ids":["sr-35ffb2d732bfae66576ee82f87c64b97"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-35ffb2d732bfae66576ee82f87c64b97","url":"https://github.com/advisories/GHSA-3x57-m5p4-rgh4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3x57-m5p4-rgh4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.661Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-35ffb2d732bfae66576ee82f87c64b97"],"technology":"zendframework/zendopenid","known_exclusions":[],"conditions_summary":"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.\n\nMoreover, 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.","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.2"]}],"null_published_at":"2026-10-31T22:12:43.399Z","source_updated_at":"2024-12-04T05:38:56.535Z","source_disclosed_at":"2024-06-07T22:28:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.661Z"}],"next_cursor":null,"snapshot_revision":"42594"}