Vulnerability	Vulnerable Version
M Information Exposure b2 is a Command Line Tool for Backblaze B2 Affected versions of this package are vulnerable to Information Exposure. 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 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. How to fix Information Exposure? Upgrade `b2` to version 3.2.1 or higher.	[,3.2.1)

Information Exposure

b2 is a Command Line Tool for Backblaze B2

Affected versions of this package are vulnerable to Information Exposure. 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 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.

How to fix Information Exposure?

Upgrade b2 to version 3.2.1 or higher.

[,3.2.1)

Go back to all versions of this package