Closed Bug 1679181 Opened 5 years ago Closed 5 years ago

Private Key Disclosure in Telemetry-airflow repository of Mozilla github account.

Categories

(Websites :: Other, defect)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: puranjanprithu, Unassigned, NeedInfo)

References

()

Details

(Keywords: reporter-external, wsec-disclosure, Whiteboard: [reporter-external] [web-bounty-form])

I used git grabber tool to search github for private api keys .
On the mozilla github account , i found a website which disclose Google Cloud Service Account credentials on its Telemetry-airflow repo.

Steps to reproduce:
Visit the following url-->
https://raw.githubusercontent.com/mozilla/telemetry-airflow/236b6feacfc4d29bfcd60ad0e2805ef55169e96c/bin/run

Repository URL : https://github.com/mozilla/telemetry-airflow
Commit (7 days ago) : 2020-11-13T19:04:30Z by anna@scholtzan.net

Flags: sec-bounty?

Thanks for the report! Can you confirm whether the creds are valid and have access to anything?

The client_email is test-account@dummy-project.iam.gserviceaccount.com, so they shouldn't have access to anything.

Flags: needinfo?(puranjanprithu)

ascholtz: can you confirm that this is a dev key without access to GCP resources?

Flags: needinfo?(ascholtz)

Can confirm the creds are public at the reported URL.

Type: task → defect
Keywords: wsec-disclosure
Whiteboard: [reporter-external] [web-bounty-form] [verif?] → [reporter-external] [web-bounty-form]

Looks like they have been added in https://github.com/mozilla/telemetry-airflow/pull/670
amiyaguchi: can probably clarify whether they have access to any GCP resources.

Flags: needinfo?(ascholtz) → needinfo?(amiyaguchi)

I can confirm that this is a fake key that is used to satisfy Airflow startup requirements. It does not map to GCP resources given the project id and service account name, though I forget the original method used to generate the keys.

Flags: needinfo?(amiyaguchi)
Group: websites-security
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: sec-bounty? → sec-bounty-
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.