DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

UIDAI puffs its chest, threatens ZDNet for the crime of journalism

Posted on March 25, 2018 by Dissent

Here we go again with shooting the messenger. Whenever someone points out leaks, breaches, or vulnerabilities involving Aadhaar data, the UIDAI often responds by denying most claims, and stating that because there’s been no breach of their database, there’s nothing to worry about. Even when there is something to worry about.

Now UIDAI is making threatening noises about suing ZDNet over a report by Zack Whittaker. Zack had reported on a researcher’s findings that a state-run utility, Indane, was leaving every person’s Aadhaar data vulnerable by failure to secure their API properly. ZDNet reported:

The utility provider Indane has access to the Aadhaar database through an API, which the company relies on to check a customer’s status and verify their identity.

But because the company hadn’t secured the API, it was possible to retrieve private data on each Aadhaar holder, regardless of whether they’re a customer of the utility provider or not.

The API’s endpoint — a URL on the company’s domain — had no access controls in place, said Saini. The affected endpoint used a hardcoded access token, which, when decoded, translates to “INDAADHAARSECURESTATUS,” allowing anyone to query Aadhaar numbers against the database without any additional authentication.

Saini also found that the API didn’t have any rate limiting in place, allowing an attacker to cycle through every permutation — potentially trillions — of Aadhaar numbers and obtain information each time a successful result is hit.

Within hours after the report appeared, the affected endpoint was taken offline.

So why is the UIDAI suggesting it might sue ZDNet? For what? Reporting on a potentially massive data breach involving Aadhaar data? What did UIDAI want ZDNet to do? Keep quiet while criminals figured out how to access all the data in their database by taking advantage of the API security issue on Indane’s site?

ZDNet reached out to UIDAI numerous times, according to Whittaker’s report. Why didn’t UIDAI respond appropriately? Why didn’t UIDAI act like an accountable agency and say, “It appears there is a potentially serious security issue involving an entity that enables access to our database. We are grateful to the researcher for discovering this so that we can work with the agency to  improve security.” Their response of just deny, deny, deny and to threaten ZDnet  is an irresponsible and dangerous strategy.

Related posts:

  • ‘Mera Aadhaar Meri Pehchan Filetype pdf’ Scare! UIDAI Warns, Precautions Must While Sharing Aadhaar Number Online
  • Aadhaar biometric data breaches trigger privacy concerns
Category: Commentaries and AnalysesNon-U.S.

Post navigation

← License, ID data lost in crash: System failure affects 66,500 Hawaii residents
“First do no harm” should be “First, secure your patient data, Doctor!” →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Mississippi Law Firm Sues Cyber Insurer Over Coverage for Scam
  • Ukrainian Hackers Wipe 47TB of Data from Top Russian Military Drone Supplier
  • Computer Whiz Gets Suspended Sentence over 2019 Revenue Agency Data Breach
  • Ministry of Defence data breach timeline
  • Hackers Can Remotely Trigger the Brakes on American Trains and the Problem Has Been Ignored for Years
  • Ransomware in Italy, strike at the Diskstation gang: hacker group leader arrested in Milan
  • A year after cyber attack, Columbus could invest $23M in cybersecurity upgrades
  • Gravity Forms Breach Hits 1M WordPress Sites
  • Stormous claims to have protected health info on 600,000 patients of North Country Healthcare. The patient data appears fake. (2)
  • Back from the Brink: District Court Clears Air Regarding Individualized Damages Assessment in Data Breach Cases

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • The EU’s Plan To Ban Private Messaging Could Have a Global Impact (Plus: What To Do About It)
  • A Balancing Act: Privacy Issues And Responding to A Federal Subpoena Investigating Transgender Care
  • Here’s What a Reproductive Police State Looks Like
  • Meta investors, Zuckerberg to square off at $8 billion trial over alleged privacy violations
  • Australian law is now clearer about clinicians’ discretion to tell our patients’ relatives about their genetic risk
  • The ICO’s AI and biometrics strategy
  • Trump Border Czar Boasts ICE Can ‘Briefly Detain’ People Based On ‘Physical Appearance’

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.