Private-key disclosure via unsanitized origin logging
Published May 29, 2020 · Updated Aug 4, 2024
Information exposure in Snyk Broker before 4.73.1 allows local users to read private keys from debug-level application logs. The Bunyan logger in lib/log.js omits the origin field from its sanitization map, so private-key material embedded in that field is written without redaction. Exposure requires LOG_LEVEL to be set to DEBUG and access to the resulting logs; the default INFO setting does not trigger the vulnerable logging path.
Summary
What happened
Information exposure in Snyk Broker before 4.73.1 allows local users to read private keys from debug-level application logs. The Bunyan logger in lib/log.js omits the origin field from its sanitization map, so private-key material embedded in that field is written without redaction. Exposure requires LOG_LEVEL to be set to DEBUG and access to the resulting logs; the default INFO setting does not trigger the vulnerable logging path.
The record
- CVE
- CVE-2020-7654
- Published
- May 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Snyk
- Product
- Snyk Broker
- Classifications
- CWE-532, T1552.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions before 4.73.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo