B2 Command Line Tool is the official command line tool for the backblaze cloud storage service. Linux and Mac releases of the B2 command-line tool version 3.2.0 and below contain a key disclosure vulnerability that, in certain conditions, can be exploited by local attackers through a time-of-check-time-of-use (TOCTOU) race condition. The command line tool saves API keys (and bucket name-to-id mapping) in a local database file ($XDG_CONFIG_HOME/b2/account_info, ~/.b2_account_info or a user-defined path) when b2 authorize-account is first run. This happens regardless of whether a valid key is provided or not. When first created, the file is world readable and is (typically a few milliseconds) later altered to be private to the user. If the directory is readable by a local attacker and the user did not yet run b2 authorize-account then during the brief period between file creation and permission modification, a local attacker can race to open the file and maintain a handle to it. This allows the local attacker to read the contents after the file after the sensitive information has been saved to it. Users that have not yet run b2 authorize-account should upgrade to B2 Command-Line Tool v3.2.1 before running it. Users that have run b2 authorize-account are safe if at the time of the file creation no other local users had read access to the local configuration file. Users that have run b2 authorize-account where the designated path could be opened by another local user should upgrade to B2 Command-Line Tool v3.2.1 and remove the database and regenerate all application keys. Note that b2 clear-account does not remove the database file and it should not be used to ensure that all open handles to the file are invalidated. If B2 Command-Line Tool cannot be upgraded to v3.2.1 due to a dependency conflict, a binary release can be used instead. Alternatively a new version could be installed within a virtualenv, or the permissions can be changed to prevent local users from opening the database file.
CVE-2022-23653
“—” beside the score: it is equal to NVD's CVSS score.
This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.7
- EG Score
- 4.7MEDIUMmedium confidence
- EG Risk
- 21EG Risk 21/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity47% × 45%Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 10th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
February 23, 2022
Last Modified
November 21, 2024
References (2)
- security-advisories@github · CVE Programhttps://github.com/Backblaze/B2_Command_Line_Tool/commit/c74029f9f75065e8f7e3c3ec8e0a23fb8204feebPatch · Third Party Advisory
- security-advisories@github · CVE Programhttps://github.com/Backblaze/B2_Command_Line_Tool/security/advisories/GHSA-8wr4-2wm6-w3prThird Party Advisory
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| b2 | 0.3.14 ... 0.0.0 (44 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 33× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 94 of 182 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-18 08:42 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-17 04:24 UTCOSV refresh
- 2026-10-16 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-12 18:59 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-11 23:25 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-03 14:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 69 moreShow fewer
- 2026-09-30 15:50 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-29 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-28 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-27 13:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-09-25 04:54 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-17 19:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-13 16:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-05 20:30 UTCOSV refresh
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-19 07:32 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-04 10:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-04 03:27 UTCOSV refresh
- 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-23 02:08 UTCEG score recompute
- 2026-07-22 22:55 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-20 17:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-19 14:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-19 02:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-18 10:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-07-17 22:29 UTCOSV refresh
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2022-23653?
When was the CVE record for CVE-2022-23653 published?
Is CVE-2022-23653 actively exploited?
What is the CVSS score of CVE-2022-23653?
How do I remediate CVE-2022-23653?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23653
Is Your Infrastructure Affected by CVE-2022-23653?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.