What is CVE-2022-23651?

CVE-2022-23651 is a medium-severity security vulnerability in b2sdk (pip), affecting versions < 1.14.1. It is fixed in 1.14.1.

How severe is CVE-2022-23651?

CVE-2022-23651 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of b2sdk are affected by CVE-2022-23651?

b2sdk (pip) versions < 1.14.1 is affected.

Is there a fix for CVE-2022-23651?

Yes. CVE-2022-23651 is fixed in 1.14.1. Upgrade to this version or later.

Is CVE-2022-23651 exploitable, and should I be worried?

Whether CVE-2022-23651 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-23651 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-23651?

Upgrade b2sdk to 1.14.1 or later.

CVE-2022-23651 in b2sdk

Q: How severe is CVE-2022-23651?

CVE-2022-23651 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of b2sdk are affected by CVE-2022-23651?

b2sdk (pip) versions < 1.14.1 is affected.

Q: Is there a fix for CVE-2022-23651?

Yes. CVE-2022-23651 is fixed in 1.14.1. Upgrade to this version or later.

Q: Is CVE-2022-23651 exploitable, and should I be worried?

Whether CVE-2022-23651 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-23651 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-23651?

Upgrade b2sdk to 1.14.1 or later.

Summary

b2-sdk-python TOCTOU application key disclosure

For more information

See the related advisory in the B2 Command Line Tool, a consumer of this SDK.

If you have any questions or comments about this advisory:

Open an issue in b2-sdk-python
Email us at [email protected]

Impact

Linux and Mac releases of the SDK version 1.14.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.

SDK users of the SqliteAccountInfo format are vulnerable while users of the InMemoryAccountInfo format are safe. The SqliteAccountInfo 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 first created, the file is world readable and is (typically a few milliseconds) later altered to be private to the user. If the directory containing the file is readable by a local attacker 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.

Consumers of this SDK who rely on it to save data using SqliteAccountInfo class should upgrade to the latest version of the SDK. Those who believe a local user might have opened a handle using this race condition, should remove the affected database files and regenerate all application keys.

CVE-2022-23651 has a CVSS score of 4.7 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.14.1); upgrading removes the vulnerable code path.

Affected versions

b2sdk (< 1.14.1)

Security releases

b2sdk → 1.14.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Users should upgrade to b2-sdk-python 1.14.1 or later.

Frequently Asked Questions

What is CVE-2022-23651? CVE-2022-23651 is a medium-severity security vulnerability in b2sdk (pip), affecting versions < 1.14.1. It is fixed in 1.14.1.
How severe is CVE-2022-23651? CVE-2022-23651 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of b2sdk are affected by CVE-2022-23651? b2sdk (pip) versions < 1.14.1 is affected.
Is there a fix for CVE-2022-23651? Yes. CVE-2022-23651 is fixed in 1.14.1. Upgrade to this version or later.
Is CVE-2022-23651 exploitable, and should I be worried? Whether CVE-2022-23651 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-23651 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-23651? Upgrade b2sdk to 1.14.1 or later.