Skip to main content
Back
ExposureAWS
2 min read

Medcall patient recordings and injury forms exposed in Amazon S3

Owner
Medcall Healthcare Advisors
When
Start unknown. Found August 24, 2018. – Aug 31, 2018Disclosed Sep 14, 2018
Entry
UpGuard observed a bucket ACL granting Everyone full control. It separately reported publicly readable medical files.

UpGuard traced the Amazon S3 bucket to Medcall Healthcare Advisors. Its access control list granted full control to the Everyone group. UpGuard examined exposed medical records and recordings and notified Medcall on August 30, 2018. By the following morning public access was closed.

What was exposed

Public reporting
UpGuard
Internet
Amazon S3
Medical files

Replaying the Medcall August 2018 exposure

  1. 1

    Full-control ACL

    August 2018

    The bucket ACL gave Everyone full control. UpGuard also confirmed that medical files were publicly readable.

  2. 2

    Public medical records

    August 2018

    Public permissions exposed recordings and injury forms. The report identified the ability to change bucket contents and permissions, without reporting malicious writes or deletions.

Impact

UpGuard found patient and doctor recordings, injury forms associated with 181 business locations and personal information about nearly 3,000 people. The bucket also permitted public writes.

Could this have been prevented?

Reject public grants on the medical-records bucket

If medical records should remain private, enable S3 Block Public Access on the bucket. Where all legitimate access can use policies, Bucket owner enforced also disables the public ACL that allowed writes and permission changes. Check object read permissions separately. AWS introduced both controls after Medcall closed the bucket.

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
UpGuard
Internet
Amazon S3
Medical files

Replaying the Medcall August 2018 exposure

1 · Full-control ACL

1 Prevented

2 · Public medical records

1 Prevented

Key facts

  • UpGuard found the exposure on August 24, 2018. It did not establish when the public grant was added.
  • The intake forms related to 181 business locations. The separate estimate of nearly 3,000 refers to people with exposed personal information.
  • The public grant permitted bucket writes and changes to permissions. UpGuard did not report a malicious change or deletion.
  • UpGuard notified Medcall on August 30, 2018, and found the bucket closed by the next morning.

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.
    Public Option: How Medical Records and Patient-Doctor Recordings Were ExposedUpGuard · Sep 14, 2018 · ResearchFirst-hand discovery, ACL permission, observed data and closure.
  2. 2.
    Blocking public access to your Amazon S3 storageAmazon Web Services · undated · Vendor reportThe four S3 Block Public Access settings and treatment of public ACLs and bucket policies.
  3. 3.
    Introducing Amazon S3 Block Public Access – another layer of protection for your accounts and bucketsAmazon Web Services · Nov 15, 2018 · Vendor reportLaunch of the bucket and account settings after these exposures.
  4. 4.
    Controlling ownership of objects and disabling ACLs for your bucketAmazon Web Services · undated · Vendor reportBucket owner enforced disables ACL authorization.

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