How to fix: Google API Key Exposed
Google API key found in source.
Why it matters
Quota theft, billing abuse.
Unrestricted Google keys can be abused.
How to fix it
- 1Restrict key to specific APIs and referrers.
Code examples
Restrict Google API key by referrer and API scope
# Restrict in Google Cloud Console > APIs & Services > Credentials
# 1. Set API restrictions: only the APIs you actually use
# 2. Set application restrictions: HTTP referrers (your domain only)
gcloud services api-keys update KEY_ID \
--allowed-referrers="https://yoursite.com/*"
# For server-side use: restrict by IP instead of referrerReferences
Detected automatically by VulnRadar. The check id is google-api-key-exposed, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Google API Key Exposed?
- VulnRadar rates this medium severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id google-api-key-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Google API Key Exposed map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.