Skip to main content
Back
ExposureAzure
2 min read

Two Wegmans customer databases exposed in Azure storage

Owner
Wegmans Food Markets
When
January 2018. Exact start day unknown. – May 12, 2021Disclosed Jun 16, 2021
Entry
The New York settlement establishes that the first Azure storage container was configured for public access. It does not identify who read the file.

New York’s attorney general said two Wegmans backup containers exposed information about more than three million consumers, including password hashes, contact details and values derived from driver’s license numbers. Wegmans dated one exposure to January 2018 and believed the other began that November. A researcher reported the first in April 2021. Wegmans found the second during its review and closed its public access on May 12.

What was exposed

Public reporting
Researcher
Wegmans
Internet
Azure storage
Customer backups

Replaying the Wegmans 2018 to 2021 exposure

  1. 1

    Account backup

    2018 to 2021

    Wegmans concluded that the first container had allowed public access since January 2018. It held customer email addresses and password hashes.

  2. 2

    Second customer database

    2018 to 2021

    Wegmans believed the second container had been public since November 2018. It found and secured it on May 12, 2021.

Impact

New York’s attorney general reported that information on more than three million consumers was exposed across the incident, including more than 830,000 New Yorkers. One container held email addresses and password hashes. Another held customer contact details and values derived from driver’s license numbers.

Could this have been prevented?

Disallow anonymous reads through the blob service

If clients can authenticate to every container in the account, disable Allow Blob anonymous access. The blob service then refuses anonymous reads even from public containers. An enabled static website can still serve files through its website endpoint. Microsoft documents the setting for API versions from April 2019 onward. Wegmans traced the first exposure to January 2018 and believed the second began that November.

Incident control assessments

2
Prevented
0
Contained
0
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.

Public reporting
Researcher
Wegmans
Internet
Azure storage
Customer backups

Replaying the Wegmans 2018 to 2021 exposure

1 · Account backup

1 Prevented

2 · Second customer database

1 Prevented

Key facts

  • The first backup contained over three million records of customer email addresses and hashed, salted account passwords. That record count is distinct from the regulator’s affected-consumer estimate.
  • Wegmans found the second container on May 12, 2021. It held contact information and checksum values derived from driver’s license numbers.
  • The attorney general identified limited log retention as an impediment to the investigation. Potential access does not establish that someone copied the databases or used customer accounts.
  • Wegmans began notifying customers on June 16, 2021. New York announced the $400,000 settlement on June 30, 2022.

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.
    Assurance of Discontinuance, In the Matter of Wegmans Food Markets, Inc. (Assurance No. 21-075)New York State Office of the Attorney General · undated · AdvisoryInvestigative findings on the two containers, dates, backup contents, reporting limits and notifications.
  2. 2.
    Attorney General James Secures $400,000 From Wegmans After Data Breach Exposed Consumers’ Personal InformationNew York State Office of the Attorney General · Jun 30, 2022 · AdvisoryConsumer counts and announced settlement.
  3. 3.
    Wegmans Notifies Customers of Database Configuration IssueWegmans Food Markets · Jun 16, 2021 · Vendor reportCompany notice, its date for learning of the issue and reported scope.
  4. 4.
    Remediate anonymous read access to blob data (Azure Resource Manager deployments)Microsoft · undated · Vendor reportAccount-level prohibition, override of container settings, effect on authorized clients and resource provider version.

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