Security

Security.

Report a vulnerability

Use GitHub private vulnerability reporting, as described in SECURITY.md. Do not open a public issue, discussion or pull request for a vulnerability.

SECURITY.md also sets out what to expect: an acknowledgement within 7 days, an initial assessment within 14 days, and which reports are in scope. It covers the latest release, v0.4.0, and main. Fixes go to main and ship in a later release. Earlier releases do not receive backports.

What CloudBurrow is not

CloudBurrow is a local emulator for development and testing. These are documented properties, not bugs:

  • The emulated APIs have no authentication. docs/configuration.md
  • Secret Manager is not a secret store. SECURITY.md
  • Cloud KMS is not a security boundary; key material is stored unencrypted. SECURITY.md
  • IAM is not a protection: stored policies are not enforced, apart from five local checks that emulate Google’s so tests can exercise them. SECURITY.md
  • It binds loopback by default; --allow-remote changes that. docs/configuration.md

Local and browser controls

v0.3.0 includes the October 17 local security review’s changes. HTTP listeners check the requested host and refuse foreign browser origins unless explicitly allowed. A page served on loopback can still call service APIs. Keep the instance on loopback and use test data.

The admin API uses a per-instance bearer token. Instance files are owner-only, and the console terminal requires a loopback peer and the console’s own origin. Credential redaction covers logs and diagnostic bundles. These checks protect local development controls. Emulated service requests remain unauthenticated, apart from the sign-ins a few services emulate for testing (Firestore with MongoDB compatibility, Memorystore AUTH and IAM auth), which accept only credentials this instance issued, and BigQuery’s per-project IAM checks of a token this instance minted.

The updated protections and their tests are described in the local security model. They are not in v0.1.0.

Supply chain

Each release archive has a SHA-256 checksum and a GitHub build attestation. The install script refuses a missing or mismatched checksum. When the GitHub CLI is installed, it also verifies the attestation unless you explicitly skip that check. The attestation ties the archive to the project’s release workflow. docs/install.md

Since v0.3.0, the release workflow builds only a commit that passed CI, and smoke-installs the prerelease on each platform's native runner before marking it latest. Platform verification

Develop locally

Found a vulnerability?

Report it privately. The report is visible only to you and the maintainers.

Get started