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

  • Hackers Using PDFs to Impersonate Microsoft, DocuSign, and More in Callback Phishing Campaigns
  • One in Five Law Firms Hit by Cyberattacks Over Past 12 Months
  • U.S. Sanctions Russian Bulletproof Hosting Provider for Supporting Cybercriminals Behind Ransomware
  • Senator Chides FBI for Weak Advice on Mobile Security
  • Cl0p cybercrime gang’s data exfiltration tool found vulnerable to RCE attacks
  • Kelly Benefits updates its 2024 data breach report: impacts 550,000 customers
  • Qantas customers involved in mammoth data breach
  • CMS Sending Letters to 103,000 Medicare beneficiaries whose info was involved in a Medicare.gov breach.
  • Esse Health provides update about April cyberattack and notifies 263,601 people
  • Terrible tales of opsec oversights: How cybercrooks get themselves caught

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

  • Kids are making deepfakes of each other, and laws aren’t keeping up
  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites

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.