Skip to main content
Back
ExposureAWS
2 min read

PayMyTab’s receipt bucket let the public browse diner records

Owner
PayMyTab
When
Receipts date to July 2018. Listing confirmed October 2019.Disclosed Nov 19, 2019
Entry
Public list access on the S3 bucket exposed the receipt inventory beyond recipients of individual links.

PayMyTab sent diners links to their receipts. The S3 bucket also allowed browsing of other receipts. An anonymous finder alerted vpnMentor, which investigated and contacted PayMyTab. Its report gave no closure date.

What was exposed

Independent research
vpnMentor
Internet
Restaurant receipts
Diner receipts

A public data exposure / PayMyTab

  1. 1

    Receipts are stored with public list access

    By October 2019

    PayMyTab provided diners with individual receipt links. Public list permission also allowed someone to browse the bucket’s receipt inventory.

  2. 2

    Receipt links expose dining details

    By October 2019

    The team examined receipts that showed diners’ contact details, meal orders and partial payment-card numbers. Direct receipt links were part of the service.

  3. 3

    The finding reaches PayMyTab

    October–November 2019

    vpnMentor examined the anonymous finder’s report and contacted PayMyTab twice. Its publication gave no closure date.

Impact

Publicly accessible restaurant receipts exposed diners’ names, contact details, meal orders and the last four digits of payment cards. The report gave no affected-diner count.

Could this have been prevented?

Keep receipt listings private and check each diner’s access

AWS Organizations introduced resource control policies in 2024. In a covered member account, a policy can block anonymous bucket listings while preserving individual receipt links. The receipt service must still verify that each diner can see only their own receipt.

Incident control assessments

1
Prevented
0
Contained
2
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
vpnMentor
Internet
Restaurant receipts
Diner receipts

A public data exposure / PayMyTab

1 · Receipts are stored with public list access

1 Prevented

2 · Receipt links expose dining details

1 Not covered

3 · The finding reaches PayMyTab

1 Not covered

Key facts

  • vpnMentor found receipts dating back to July 2, 2018, from diners who requested an emailed receipt. The date that public listing began was unknown.
  • The team received the finding on October 18, 2019. It contacted PayMyTab on October 22 and again on October 27.
  • vpnMentor described potential fraud but reported no evidence of fraud or copying by other readers.
  • vpnMentor published its report on November 19, 2019. It did not give a closure date.

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.
    Report: Mobile Payments Provider Leaks Data of US Restaurant Diners NationwidevpnMentor · Nov 19, 2019 · ResearchPublic receipt access, list permission, intended diner links and notification attempts

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