{"id":3461,"date":"2026-11-07T07:08:33","date_gmt":"2026-11-07T07:08:33","guid":{"rendered":"https:\/\/smartcryptosecurity.com\/?p=3461"},"modified":"2026-11-07T07:08:33","modified_gmt":"2026-11-07T07:08:33","slug":"stir-shaken-framework-plagued-by-cryptographic-flaws-privacy-risks-and-widespread-noncompliance-new-study-reveals","status":"publish","type":"post","link":"https:\/\/smartcryptosecurity.com\/?p=3461","title":{"rendered":"STIR\/SHAKEN Framework Plagued by Cryptographic Flaws, Privacy Risks, and Widespread Noncompliance, New Study Reveals"},"content":{"rendered":"<p>Scams, fraud, and deceptive robocalls have long plagued the modern telecommunications landscape. To combat these relentless intrusions, fraudsters frequently employ call spoofing, disguising their true identities by impersonating trusted entities, local businesses, or government agencies to deceive unsuspecting victims. This deceptive practice makes it extraordinarily difficult for everyday consumers and automated filtering systems alike to reliably detect and intercept fraudulent calls before they reach the handset. In a decisive regulatory response to this escalating national security and consumer protection challenge, the United States government mandated the implementation of a comprehensive new suite of cryptographic protocols known as STIR\/SHAKEN in 2019. <\/p>\n<p>Designed to restore trust in the telephone network, STIR\/SHAKEN requires telecommunications providers to attach a cryptographically signed assertion containing the caller\u2019s identity and associated metadata directly into the routing headers of telephone calls. This digital signature serves a dual purpose: it authentically conveys verified caller metadata between disparate service providers as a call traverses complex routing networks, and it creates reportable, verifiable evidence of malicious activity should a provider originate fraudulent calls. However, a comprehensive new research paper titled &quot;STIR\/SHAKEN: A Cocktail of Cryptographic Clumsiness,&quot; authored by Josh Brown and Paul Grubbs from the University of Michigan\u2013Ann Arbor alongside Matthew Hardeman from Low-Latency Communications, investigates whether this federally mandated framework actually achieves its foundational security goals\u2014and at what profound cost to the broader telephone ecosystem.<\/p>\n<p>The findings of the study reveal a system hampered by severe structural vulnerabilities, widespread regulatory noncompliance, and alarming unintended consequences for consumer privacy. Analyzing a full year of live STIR\/SHAKEN certificates observed in production telephone traffic, the researchers discovered a public key infrastructure riddled with noncompliance, finding that nearly half of all valid certificates in the wild actively violate established technical specifications. Furthermore, the architecture contains critical loopholes that allow a malicious or negligent provider to prevent the later verification of a STIR\/SHAKEN assertion simply by taking its signing certificate offline after the call has been initiated. <\/p>\n<p>Compounding these structural weaknesses, the study uncovered a critical header-malleability flaw within the protocol&#8217;s implementation. The researchers verified this vulnerability during real-world test calls placed with the assistance of a cooperating telecommunications provider, demonstrating that an attacker can exploit the flaw to cause a blatantly spoofed caller ID to be displayed as officially verified on consumer telephone handsets. These systemic flaws expose fundamental gaps in how the protocol was designed and deployed across the national telecommunications grid.<\/p>\n<p>Beyond these technical and cryptographic vulnerabilities, the deployment of STIR\/SHAKEN has introduced profound new systemic harms to the privacy of everyday phone users. According to the research paper, these unprecedented privacy violations manifest in two distinct and troubling ways. First, the core mechanism of signing call metadata renders call events cryptographically non-repudiable. For the first time in the 150-year history of the public telephone network, there now exists publicly verifiable, permanent proof that a specific phone call took place between two parties. <\/p>\n<p>Second, the sheer technical complexity of implementing STIR\/SHAKEN has driven telecommunications providers to outsource their signing and verification processes to third-party vendors. Out of 29 providers surveyed by the researchers, roughly half outsource these critical functions, with the vast majority relying on a small handful of dominant commercial vendors. This mass outsourcing has triggered widespread, unregulated leakage of sensitive call metadata to off-path third parties operating entirely outside the direct provider-consumer relationship. <\/p>\n<p>The scope of this data aggregation is vast. For instance, one such off-path third party, Neustar, was acquired in 2021 by TransUnion, one of the three major nationwide U.S. credit reporting bureaus. Neustar routinely authenticates more than 30 billion telephone calls every month. Following the acquisition, TransUnion began offering a commercial product known as &quot;Phone Behavior Intelligence,&quot; which aggressively advertises deep &quot;insight into billions of call transactions&quot; obtained directly through its expansive and privileged carrier relationships. These structural privacy incursions are further compounded by glaring local implementation failures; during their evaluation, the researchers identified provider implementations that completely break the federally mandated *67 caller-privacy mechanism, inadvertently exposing caller identities that users explicitly sought to conceal.<\/p>\n<p>To address these profound architectural and privacy shortcomings, the paper proposes a series of targeted technical solutions. To mend the fractured public key infrastructure, the authors argue that STIR\/SHAKEN must adopt certificate transparency principles. Implementing a public certificate log would permanently eliminate the ability of rogue or negligent providers to evade accountability by taking their signing certificates offline to defeat post-call verification. <\/p>\n<p>The remaining cryptographic solutions proposed by the researchers require overcoming a fundamental prerequisite that the current STIR\/SHAKEN framework cannot meet: the originating service provider must be able to securely learn the public key of the destination provider. To resolve this architectural roadblock, the authors designed a fully backwards-compatible key discovery mechanism that cleverly leverages standard Session Initiation Protocol (SIP) error messages. <\/p>\n<p>To confront the severe privacy harms directly, the researchers propose replacing STIR\/SHAKEN&#8217;s traditional signatures with asymmetric message franking (AMF). This cryptographic adjustment restores deniability to call metadata, ensuring that calls are no longer permanently non-repudiable. Furthermore, by issuing these asymmetric message frankings blindly, call metadata remains completely hidden from the third-party vendors handling outsourced signing duties. To achieve this, the authors designed the first-ever blind signing protocol tailored for the AMF construction developed by Tyagi and colleagues, complete with rigorous new security definitions that capture unique operational requirements such as verifier-hiding blindness. Through this work, the researchers initiate the formal academic study of blind signing protocols specifically for designated-verifier signatures, contributing a foundational cryptographic advancement expected to generate independent interest across the computer science and security research communities.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Scams, fraud, and deceptive robocalls have long plagued the modern telecommunications landscape. To combat these&#8230;<\/p>\n","protected":false},"author":2,"featured_media":3460,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[676],"tags":[678,1002,607,334,56,677,2895,2894,211,214,838,1093,1504,2893,2286,1217],"class_list":["post-3461","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cryptography-math","tag-algorithms","tag-cryptographic","tag-cryptography","tag-flaws","tag-framework","tag-math","tag-noncompliance","tag-plagued","tag-privacy","tag-research","tag-reveals","tag-risks","tag-shaken","tag-stir","tag-study","tag-widespread"],"_links":{"self":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3461","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3461"}],"version-history":[{"count":0,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/posts\/3461\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=\/wp\/v2\/media\/3460"}],"wp:attachment":[{"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartcryptosecurity.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}