Local application-key disclosure via delayed permission hardening
Published Feb 23, 2022 · Updated Apr 23, 2025
Key disclosure in Backblaze B2 Python SDK before 1.14.1 allows local users to read API keys through a file-creation race. SqliteAccountInfo creates its SQLite database with permissive access, writes credentials, and only afterward changes the file to owner-only mode. Exploitation requires a readable containing directory and winning the brief creation-to-chmod race; InMemoryAccountInfo users and Windows releases are unaffected.
Summary
What happened
Key disclosure in Backblaze B2 Python SDK before 1.14.1 allows local users to read API keys through a file-creation race. SqliteAccountInfo creates its SQLite database with permissive access, writes credentials, and only afterward changes the file to owner-only mode. Exploitation requires a readable containing directory and winning the brief creation-to-chmod race; InMemoryAccountInfo users and Windows releases are unaffected.
The record
- CVE
- CVE-2022-23651
- Published
- Feb 23, 2022
- Updated
- Apr 23, 2025
- Vendor
- Backblaze
- Product
- B2 Python SDK
- Classifications
- CWE-276, CWE-367, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 1.14.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