Menu

WatchGuard AuthPoint's callback trusted a signed header too much
📰

WatchGuard AuthPoint's callback trusted a signed header too much

DEV Community: authentication·yutianle·6 days ago
#B3RQAsud
Reading 0:00
15s threshold

WatchGuard AuthPoint's callback trusted a signed header too much

Authentication gateways sit between an identity provider and the applications that depend on it. They are expected to reject forged login results even when an attacker can reach the callback endpoint. WatchGuard AuthPoint Gateway had a defect in exactly that location: the LDAP authentication callback validated a header signature but did not bind the signed result to the transaction fields in the request body.

WatchGuard's advisory for CVE-2026-121637 describes improper integrity validation in the LDAP authentication callback. An attacker who has obtained a valid header signature can forge the authentication result and transaction identifier in the request body, producing an unauthorized session outcome. A second issue, CVE-2026-121638, involves improper certificate validation and creates a man-in-the-middle risk.

The vendor lists AuthPoint Authentication Gateway versions from 1.0 before 7.6.0 as affected and 7.6.0 as the fixed release.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.