Skip to main content
Back
ExposureAWS
2 min read

A public database exposed a copy of the Dow Jones Watchlist

Owner
Dow Jones Watchlist data
When
Found February 22, 2019. Opening date unknown.Disclosed Feb 27, 2019
Entry
A public Elasticsearch cluster allowed anyone to read the watchlist.

Security Discovery found the watchlist on a public Elasticsearch cluster and notified Dow Jones on February 22, 2019. The researcher later reported that the database had gone offline. The exposure window is unknown.

What was exposed

Independent research
Security Discovery
Internet
Watchlist hosting
Watchlist records

A public data exposure / Dow Jones Watchlist data

  1. 1

    The watchlist database is reachable from the internet

    By February 22, 2019

    An Elasticsearch cluster was reachable from the public internet. Dow Jones said its initial review pointed to an authorized third party’s AWS server.

  2. 2

    The researcher inspects the watchlist

    February 22, 2019

    Security Discovery examined 2,418,862 watchlist records in a 4.4 GB database. The contents included individual and organizational risk-screening profiles.

  3. 3

    The watchlist copy is taken offline

    After notification, exact date unknown

    The researcher notified Dow Jones on February 22. The report confirms the database went offline but gives no takedown date.

Impact

A public Elasticsearch cluster exposed 2,418,862 watchlist records. The 4.4 GB copy included risk-screening profiles and the lists on which subjects appeared.

Could this have been prevented?

Restrict who can reach and query the watchlist

Require authentication for watchlist searches. If your cluster uses AWS security groups, restrict inbound access across every attached group. The report does not identify the network path to this database.

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
Watchlist hosting
Watchlist records

A public data exposure / Dow Jones Watchlist data

1 · The watchlist database is reachable from the internet

1 Not covered

2 · The researcher inspects the watchlist

1 Not covered

3 · The watchlist copy is taken offline

1 Not covered

Key facts

  • Security Discovery found the public cluster and notified Dow Jones on February 22, 2019.
  • Dow Jones said the underlying data came from public sources. The researcher found that the assembled dataset itself was openly accessible.
  • The investigator counted records. The report gives no count of unique people or unauthorized downloads.
  • The 2017 Dow Jones subscriber exposure involved an S3 bucket. The researcher found the 2019 watchlist copy on a separate Elasticsearch cluster.

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.
    Dow Jones Risk Screening Watchlist Exposed Publicly in a Major Data BreachSecurity Discovery · Feb 27, 2019 · ResearchPublic Elasticsearch cluster, record count, disclosure and Dow Jones statement

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