Files
elabore-charms/plausible/README.org
Valentin Lab 8f73a16f5c fix: [plausible] close the unauthenticated code execution of `/storybook with 3.2.1`
Plausible Community Edition up to ``3.2.0`` serves ``/storybook``, which
compiles and runs code sent by any visitor (CVE-2026-8467,
GHSA-mhcv-h7gf-57cf).  It was used to install cryptocurrency miners in
the container of a ``3.0.1`` deployment.  ``3.2.1`` removes the endpoint.

- Use ``docker.0k.io/plausible:3.2.1`` (from
  ``ghcr.io/plausible/community-edition:v3.2.1``).  The database
  migrations run at start as before; ``3.0.1`` data migrates without
  manual step.
- The default web-proxy rules refuse ``/storybook``, in case an older
  image is ever deployed again.
- The Erlang release cookie of the image is created when the image is
  built, so it is the same on every installation.  The ``init`` hook now
  generates one per installation (``release-cookie``) and sets
  ``RELEASE_DISTRIBUTION`` to ``none``: this single node opens no
  ``epmd`` nor distribution port.

Assisted-by: Claude:claude-opus-5-5
2026-10-27 11:23:21 +01:00

44 lines
1.5 KiB
Org Mode

# -*- ispell-local-dictionary: "english" -*-
* Info
From: https://github.com/plausible/community-edition/
* Usage
#+begin_src yaml
plausible:
relations:
web-proxy:
frontend:
domain: stats.example.com
#+end_src
A =clickhouse= (statistics) and a =postgres= (accounts, sites) service
are added automatically.
* Security
- Plausible before 3.2.1 serves =/storybook=, which runs any code sent
to it without authentication (CVE-2026-8467, GHSA-mhcv-h7gf-57cf).
This charm uses 3.2.1, and its default web-proxy rules refuse
=/storybook= in case an older image is deployed again.
- The Erlang release cookie of the image is generated when the image is
built, so it is the same for every installation. The charm generates
its own (=release-cookie= in the service datastore) and sets
=RELEASE_DISTRIBUTION= to =none=: this single node opens no =epmd= nor
Erlang distribution port.
* Upgrading from 3.0.x
- Migrations run at each start (=db migrate= in the entrypoint), for
both PostgreSQL and ClickHouse. They cannot be reverted: back up both
databases first.
- Deploy together with the =clickhouse= charm of the same revision: the
ClickHouse low-memory profile moved to =users.d= (upstream change of
3.2.0).
- Sites keep working with their existing tracking snippet.
- Changing =secret-key= signs everybody out, invalidates every API key,
and makes the 2FA secrets unreadable unless =TOTP_VAULT_KEY= is set
to the key derived from the previous one.