Prometheus through 3.15.1 Credential Leak via remote_write Cross-Host Redirects
Why It Matters
Analysis dossierWhy It Matters
Prometheus through 3.15.1 contains a credential leak vulnerability that allows attackers to capture Azure AD or Google IAM bearer tokens by redirecting remote_write requests to another host. Attackers controlling the remote-write endpoint or a redirecting server can return a 3xx to their host and replay the token, for example to write metrics to the victim's backend.
Medium
Unknown
Unknown
Risk basis: Microsoft or Microsoft-managed product relevance; Source severity; no confirmed exploitation signal
Affected Products & Remediation
2 source-backed productsVendor or catalog guidance (source)
- Microsoft MSRC: Release Notes
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Unknown
- Exploited (source statement)
- Unknown
- Publicly disclosed (source)
- Unknown
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched credential-exposure (CWE-522); network-unauthenticated (CVSS AV:N, CVSS PR:N, CVSS UI:N)
Exposure
- Identify affected installations and the credential-handling feature described by the source.Telemetry: Application inventory · The CWE alone does not establish which secrets were exposed. · Rule credential-exposure
- Identify devices reporting this CVE and note which expose the affected service to untrusted networks.Telemetry: DeviceTvmSoftwareVulnerabilities · A network-reachable, no-privilege vector makes internet-facing instances the first exposure question. · Rule network-unauthenticated
Exploitation evidence
- Review anomalous sign-ins for accounts that could be affected after confirming the exposure path.Telemetry: SigninLogs · Sign-in review is conditional; no compromise is presumed. · Rule credential-exposure
Show more (2)
Exploitation evidence
- Review inbound connections to the affected service from unexpected sources since the advisory date.Telemetry: DeviceNetworkEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule network-unauthenticated
Response
- Follow the source mitigation and rotate credentials only where exposure is confirmed or advised.Telemetry: Identity audit logs · Credential response should follow evidence and vendor guidance. · Rule credential-exposure
CISA KEV Record
CISA KEV status was not determined for this record.
Change History & Source Data
— No recorded material change
- CNA / source
- disclosure@vulncheck.com
- Record status · verification
- UPDATED · NVD API
- CPE
- Unknown
Evidence & Provenance
— No published hunting query names this record. Browse community and library queries instead.
Looking up related community queries…