One Article Review
| Source |  CVE Liste |
|---|---|
| Identifiant | 4175469 |
| Date de publication | 2022-02-23 23:15:07 (vue: 2022-02-24 02:06:10) |
| Titre | CVE-2022-23653 |
| Texte | 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. |
| Envoyé | Oui |
| Condensat | 2022 23653 `$xdg `b2 `~/ access account account` after all allows altered alternatively another api application are attacker attackers authorize backblaze been before below between binary brief bucket can cannot certain changed check clear cloud command condition conditions config configuration conflict contain contents could created creation cve database defined dependency designated did directory disclosure does due during ensure exploited file first from had handle handles happens has have home/b2/account info` information installed instead invalidated key keys later line linux local mac maintain mapping milliseconds modification name new not note official open opened opening other path period permission permissions prevent private provided race read readable regardless regenerate release releases remove run running safe saved saves sensitive service should storage then through time toctou tool typically upgrade upgraded use used user users valid version virtualenv vulnerability when where whether within world yet |
| Tags | Tool Vulnerability |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.