November 9, 2026
The Dangling CDN Record That Unlocked SSO
A 2017 Uber disclosure shows why cookie-sharing SSO is only as safe as every sibling hostname

By Muhammad Asim Shahzad
2 min read
AI disclosure: This article was drafted with AI assistance as an analytical case study of a public disclosure. It is not my own discovery.
A leftover DNS alias is easy to file as housekeeping. Arne Swinnen reported that an Uber hostname still pointed at a CloudFront distribution nobody owned, and that Uber's then-new cookie-sharing single sign-on treated sibling hostnames as part of the same trust domain. Together, the two issues could escalate into impersonation across properties protected by that sign-on. Uber removed the dangling record and paid $5,000 for the combined findings, per the researcher.
Vulnerability Overview
- Type: Subdomain takeover escalating to SSO session compromise
- CWE (analytical mapping, not from the source): CWE-283, CWE-565
- CVE: Not stated in the disclosure
- Severity/CVSS: Not reported. Bounty: $5,000 (source-reported)
What Happened (high level)
Uber had moved toward SSO that shared session cookies across sibling hostnames.
Separately, a static-content hostname still had a DNS alias to Amazon CloudFront, but the matching distribution was no longer registered. That dangling pointer let the researcher claim the unused CDN slot and serve content on an Uber hostname. Parent-domain cookies are visible to sibling hosts, so an attacker-controlled hostname inside that cookie scope can observe SSO material the browser sends there.
Uber had tried to shrink the lifetime of shared cookies and had added a login anti-forgery check. Those countermeasures did not stop a relayed sign-on once a sibling hostname was attacker-controlled. This article does not reconstruct that relay.
He submitted the report on 7 April 2017. Uber removed the DNS alias on 7 June 2017 after he noted he still controlled the hostname, paid a total of $5,000, and confirmed an extra binding check on session use on 7 July 2017.
Impact
The researcher described an authentication bypass of Uber's SSO, reaching properties that SSO protected, including rider, partner, developer, and vault-style applications. Already-authenticated sessions were in scope, not merely visitors of the neglected static hostname.
Remediation & Defense-in-Depth (my own analysis)
- Treat unclaimed cloud aliases as production incidents. Continuously inventory canonical names that point at CDNs, load balancers and SaaS vendors, and fail a release when the provider no longer has a matching owned resource.
# Pseudocode: block deploys when a CNAME target does not claim the hostname
def assert_alias_owned(hostname, provider):
target = dns.cname(hostname)
if target is None:
return
if not provider.distribution_claims(hostname):
raise DanglingAlias(hostname)
def issue_session(response, token):
# Host-only cookie: omit Domain so sibling hostnames cannot read it
response.set_cookie(
"session", token,
secure=True, httponly=True, samesite="Lax",
path="/",
)# Pseudocode: block deploys when a CNAME target does not claim the hostname
def assert_alias_owned(hostname, provider):
target = dns.cname(hostname)
if target is None:
return
if not provider.distribution_claims(hostname):
raise DanglingAlias(hostname)
def issue_session(response, token):
# Host-only cookie: omit Domain so sibling hostnames cannot read it
response.set_cookie(
"session", token,
secure=True, httponly=True, samesite="Lax",
path="/",
)-
Stop sharing session cookies with every sibling. Issue host-only cookies, or the __Host- prefix, instead of parent-domain cookies. A marketing hostname should never observe a sign-on cookie.
-
Prefer token-based SSO with exact redirect allowlists. Swinnen recommended returning to OAuth-style federation.
-
Scope review to the real trust domain. Every hostname that can see parent-domain cookies belongs in security testing and in the bug-bounty policy, including leftovers from old campaigns.
-
Treat address binding as extra depth, not the fix. Uber also added an address-binding check on session use. The researcher noted residual risk when attacker and victim share an external address.
Key Takeaways
Dangling cloud aliases are takeover primitives, not leftover DNS trivia.
Cookie-sharing SSO inherits the weakest sibling hostname in the parent domain.
Ownership checks belong in deploy automation, not in a yearly spreadsheet.
Credit & Sources
Research by Arne Swinnen: Authentication bypass on Uber's Single Sign-On via subdomain takeover (25 June 2017). Facts come from that post; analysis, code and remediation are original suggestions.
Disclaimer: Educational and defensive use only. Reported in April 2017 and mitigated that June and July. This article intentionally omits reproduction details.
Source: https://www.arneswinnen.net/2017/06/authentication-bypass-on-ubers-sso-via-subdomain-takeover/