Skip to content

ForgetBase v0.1.0-beta.5

Pre-release
Pre-release

Choose a tag to compare

@jremick jremick released this 05 Sep 08:54
· 76 commits to main since this release
80a2671

ForgetBase beta.5 fixes six security gaps in outbound requests, OIDC, logging, browser-origin handling and attachment processing. It also patches the application container base layers.

Changes

  • Reject redirects on credential-bearing SDK, model, embedding, OIDC and worker requests.
  • Require the configured OIDC issuer, HTTPS outside loopback development, required ID-token claims, and bounded discovery/token responses.
  • Exclude query strings, credentials and exception details from API responses and proxy logs.
  • Reject unsafe browser requests from disallowed origins before changing a session.
  • Inspect Office ZIP metadata with bounded decompression and reject concealed macros or malformed archives.
  • Reject binary request bodies on unrelated routes before parsing or authentication.
  • Patch the Node image OpenSSL packages, use the slim Nginx 1.30.4 image, refresh the Compose PostgreSQL 17 image, and configure isolated browser tests with their selected origins.

Source: 80a2671f3c86786814c8dfefa4ff8586e669447c. Changes: #20, #21.

Verification

  • 492 tests across 43 files passed with PostgreSQL and no skips; 58 API/SDK/CLI/MCP contract checks passed.
  • CI, isolated full-stack proof and CodeQL passed for the release commit. GitHub reports no open CodeQL, secret-scanning or Dependabot alerts.
  • The existing askbase.dev installation runs the release source across API, worker, web and proxy. The running application services have the patched OpenSSL packages. Hosted database and scanner services retain their existing deployments, recorded in the verification asset; the PostgreSQL image refresh applies to Compose installations.
  • Hosted browser UAT passed 148 admin and 89 reader checks; split-origin UAT passed 129 checks. Synthetic fixtures and credentials were removed. Representative desktop/mobile screenshots were inspected; policy and approval form screenshots are layout evidence, not policy-mutation verification.
  • Pre- and post-release recovery snapshots restored successfully, including access and publication checks. All 22 checked canonical tables retain their original records. Live recovery verified an empty attachment store; isolated full-stack CI also verified a database/blob recovery set with an attachment.
  • Clean installation, typecheck, build, deployment defaults, release proof and secret scans passed. The production JavaScript dependency audit reported zero advisories. Two independent artifact preparations produced identical source archives and manifests.

Compatibility and upgrade

Use the source archive and checksums below, or check out this tag. Follow the deployment and recovery runbook. Preserve a matched database and attachment recovery set before upgrading. No application schema migration or JavaScript dependency change is added.

Provider and API URLs must point directly to their final endpoint. OIDC requires the exact configured issuer and HTTPS outside loopback development. Office uploads reject encrypted, ZIP64 and unsupported archives. Error responses use stable codes instead of exception text.

Security limits

The patched amd64 Node base layer and slim Nginx image each report zero OS-package findings. The updated PostgreSQL and pinned ClamAV images retain 409 and 240 vendor-advisory records respectively, including critical and high scanner labels. No stable-distribution fix is listed for those high/critical records. These counts include repeated source-package findings and do not establish application exploitability. Some have narrower vendor assessments; six lower-severity PostgreSQL-image records still have a listed fix absent from the upstream image. The container security record and attached scans retain this evidence. Final provider-built image layers are outside the OS scan.

This remains an experimental prerelease for self-hosted trials with synthetic data, one API replica and filesystem attachments. It does not promise production support or stable compatibility. External identity providers, paid model quality, managed upgrades and local-agent candidate branches are outside this release verification.

Report bugs through Issues and suspected vulnerabilities through private vulnerability reporting.