How to fix: Hard-coded secret in source (low-risk identifier)
A Firebase Realtime Database URL is present in the source. This is a hostname, not a credential: it contains no key or token material.
Why it matters
The URL alone grants no access. The actual exposure to watch for is whether the database's security rules allow unauthenticated read/write: the hostname just confirms which project to check.
Flagged as informational-level so it is visible in a review without inflating the scan's overall severity: knowing a site uses Firebase RTDB is useful context, not evidence of a leak.
How to fix it
- 1Review Firestore/RTDB security rules to confirm they require authentication
- 2Enable Firebase App Check if the database is publicly reachable
Code examples
Firestore rules: require authentication
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /{document=**} {
allow read, write: if false;
}
}
}References
Detected automatically by VulnRadar. The check id is hardcoded-secrets-low-risk, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Hard-coded secret in source (low-risk identifier)?
- VulnRadar rates this low severity in the code 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 hardcoded-secrets-low-risk, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Hard-coded secret in source (low-risk identifier) 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.