Skip to main content
Back
ExposureAWS
2 min read

An open Elasticsearch database exposed 257,287 legal documents

Owner
Unidentified database operator
When
Found March 2, 2019. Opening date unknown.Disclosed Mar 15, 2019
Entry
An AWS-hosted Elasticsearch cluster allowed access without a password.

Security Discovery found the documents on an AWS-hosted server on March 2. The researcher contacted one possible operator. Nearly two weeks later the database was unreachable. He could not confirm who owned it or who secured it.

What was exposed

Independent research
Security Discovery
Internet
Legal records
Legal documents

A public data exposure / Unauthenticated database

  1. 1

    A legal document database is public

    By March 2, 2019

    An Elasticsearch database hosted on a US AWS server was open without a password. Its owner was never confirmed.

  2. 2

    A researcher examines the legal records

    March 2, 2019

    Bob Diachenko found 257,287 legal documents marked as not designated for publication. The database totaled 4.7 GB.

  3. 3

    The database goes offline

    March 2019

    The researcher notified a suspected owner and received no reply. Almost two weeks later, he found that the database was secured and unreachable.

Impact

An AWS-hosted Elasticsearch database exposed 257,287 legal documents marked as not designated for publication. Security Discovery measured the database at 4.7 GB.

Could this have been prevented?

Require authentication for legal document searches

Require the database to authenticate readers and authorize access to the document index. If you operate the service on AWS, identify the actual network entry point before choosing an AWS network control.

Incident control assessments

0
Prevented
0
Contained
3
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Independent research
Security Discovery
Internet
Legal records
Legal documents

A public data exposure / Unauthenticated database

1 · A legal document database is public

1 Not covered

2 · A researcher examines the legal records

1 Not covered

3 · The database goes offline

1 Not covered

Key facts

  • The researcher found the open database on March 2, 2019. The date it first became public is unknown.
  • The 257,287 figure counts legal documents. The report does not give a count of people or cases.
  • The researcher notified one suspected owner and later considered another possibility. Neither attribution was confirmed.
  • The database was unreachable almost two weeks after the notification. The report gives no exact closure date or evidence of another reader.

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    A legal analytics company exposed passwordless database with sensitive documentsSecurity Discovery · Mar 15, 2019 · ResearchFirst-hand discovery, material inspected, attribution and disclosure chronology

The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.

More cloud attack breakdowns

All breakdowns