Security-response owner: Backblaze Security. Repository maintainers triage reports with them.
The latest release of b2sdk (currently 2.13.x) receives security fixes. Every apiver layer
(b2sdk.v0..b2sdk.v3) inside that release is covered. Earlier releases are not patched in place;
upgrade to the newest release to receive fixes.
| Version | Supported |
|---|---|
Latest release (2.13.x) |
Yes |
| Older releases | No |
Do not file a public GitHub issue for a security vulnerability.
Instead, report it privately via GitHub Security Advisories:
- Go to the Security tab of this repository
- Click Report a vulnerability
- Provide a clear description, the affected version, reproduction steps, and impact assessment
You can also email security@backblaze.com if you cannot use GitHub Security Advisories.
- Acknowledgement within 3 business days
- Initial assessment within 7 business days
- Coordinated disclosure once a fix is available, shipped as a patch release with a changelog entry and a GitHub security advisory
In scope:
- Credential-handling flaws in
b2sdk: application keys, authorization tokens or SSE-C keys exposed in logs, exception messages,repr, or sent to unintended hosts - Account-info storage:
SqliteAccountInfofiles created readable by other users, or credentials cached where the caller did not ask - Transport flaws: TLS verification bypassed, or requests sent outside the key's bucket or prefix scope
- Sync and download path handling that writes outside the destination folder
- Denial of service reachable through the public API, such as unbounded retries or thread leaks triggered by server responses
Out of scope:
- Vulnerabilities in the Backblaze B2 service itself — report those to Backblaze directly
- Misuse of credentials by the calling application, such as embedding a master key in client code
- Issues requiring root or local access on the machine running the application
- Credentials: application keys go to
B2Api.authorize_accountand only to the B2 authorize endpoint; the token returned is kept in the account-info store and sent in theAuthorizationheader. - Account info:
SqliteAccountInfocreates its database with owner-only permissions before writing credentials to it. - SSE-C keys: customer-provided keys travel in request headers on uploads and downloads, and as
customerKeyfields in JSON request bodies on large-file start (serverSideEncryption) and server-side copy (sourceServerSideEncryption,destinationServerSideEncryption). They are not persisted. If you log requests, redact encryption keys in both headers and bodies. - Transport: all B2 API traffic uses HTTPS through
requests, with certificates fromcertifi. - Tests and CI: integration tests read
B2_TEST_APPLICATION_KEY_IDandB2_TEST_APPLICATION_KEYfrom repository secrets. The.sdkharnesschecks refuse any non-loopback endpoint and ambientB2_*credentials.
- Use application keys scoped to specific buckets, prefixes and capabilities.
- Never embed an application key in code shipped to end users; issue download authorizations from a backend instead.
- Rotate application keys regularly.
- Use SSE-B2 or SSE-C for encryption at rest, and Object Lock for compliance-sensitive data.