DataBreaches.Net

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

Database leaks 250K legal documents, some marked ‘not designated for publication’

Posted on March 16, 2019 by Dissent

Catalin Cimpanu reports:

A database containing 257,287 legal documents, with some marked as “not designated for publication,” was left exposed on the public internet without a password, allowing anyone to access and download a treasure trove of sensitive legal materials.

The database, which was left online for roughly two weeks, contained unpublished legal documents relating to US court cases, the security researcher who found it told ZDNet.

Read more on ZDNet.

But were the files really a trove of sensitive materials?  I don’t think “unpublished” means what the researcher seemed to be suggesting it might mean.  As I understand it (and I could be wrong, of course), an unpublished opinion or one “not designated for publication” is not one that has to be kept sealed or confidential. It is simply an opinion that the court doesn’t want future cases citing as precedential. The opinions are available and I think they can even be cited to try to persuade a court, but they are not precedential. I’ve reached out to a lawyer to try to get clarification on my understanding, but if I’m correct, then:

What did the researcher really find in terms of sensitivity or confidentiality? Did any of the filings contain sensitive information? The researcher’s report offers no redacted samples of any filing had been marked “SEALED” or “CONFIDENTIAL” or anything like that, so DataBreaches.net reached out to Security Discovery to see if there were sealed files in the leak.  Bob Diachenko responded that

there were references to “sealed” cases throughout the texts, with descriptions of the cases.  But most of the cases were marked as ‘not designated for publication’, ‘not to be published in the official reports’ + references to sealed cases.

So it’s still not clear whether there any actual exhibits or files that were stamped “sealed” or “confidential” or if there was just sanitized references to sealed cases.

In any event, the leak shouldn’t have happened, and it’s not even clear whose leak it was.

 


Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
  • Months After Being Notified, a Software Vendor is Still Exposing Confidential and Sealed Court Records
Category: Breach Incidents

Post navigation

← Some job applicants are first learning about the May, 2018 JobScience breach. Why?
Student information: Mississippi reaches agreement with Questar over data breach →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.