DEV Community

jeffrey
jeffrey

Posted on

Bichon title matches should lead with mailbox access and archive encryption

Bichon title matches should lead with mailbox access and archive encryption

Bichon is a self-hosted email archiver with a web interface, API, role-based access control, and mailbox synchronization. An archive can contain years of messages and attachments. The most important review questions concern who can read that content and which stored secrets can connect Bichon back to source mailboxes.

Observation

At 07:51 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="Bichon" returned 1 match. title="Bichon" returned 146 matches.

The title query is the larger population and may include unrelated pages with the same word. The single application match is a narrow technical signal, not proof of a vulnerable host. Both sets should be validated against Bichon's documented login and API paths.

Defaults and roles

Bichon's quick-start documentation lists a default administrator username and password. Any deployment that retains that default has an immediate credential problem. The authentication documentation describes configurable web token expiration and TOTP multi-factor authentication. The access-control documentation describes global roles and account-scoped roles, plus a metrics_only token for the metrics endpoint.

Inventory users, global roles, account assignments, API tokens, MFA state, and token expiration. Then map the mail accounts each user can read. A support role that can manage tags should not automatically see every mailbox unless that is an explicit decision.

What the archive protects

Bichon's security documentation distinguishes values it encrypts from the data root it does not protect as a whole. Stored secrets such as IMAP passwords and OAuth tokens can use an encryption password. Tantivy indexes and backups have documented limits: someone with read access to the data root may be able to read archive content. That makes filesystem ownership, backup access, and key separation part of the application security boundary.

Review where the data root lives, who can read it, whether backups are encrypted outside Bichon, and whether the encryption password is stored away from the archive host. Test restore with the key unavailable and with the key present.

Useful checks include the default admin credential, MFA enrollment, a user removed from an account-scoped role, a metrics token used against another route, and an API token after logout or expiration. These are targeted tests of the documented controls.

References

Top comments (0)