DEV Community

kozhevniko
kozhevniko

Posted on

Suwayomi inventory must identify the authentication mode, not just the web UI

Suwayomi inventory must identify the authentication mode, not just the web UI

Suwayomi Server, formerly associated with Tachidesk, runs manga sources and serves a library to web and desktop clients. Its web interface can look the same under several authentication modes. Inventory that records only the page title cannot tell whether the API is open, protected by HTTP Basic authentication, or using a JWT-based UI login.

The ZoomEye count-only observation on 2026-11-16 found 0 app matches, 1,278 title matches, and 7,471 http.body matches for Suwayomi. The probes used sub_type=all, page 1, and pagesize 1. The title result is a candidate set. A body match may be a project mention, a source list, or documentation.

The official configuration wiki documents server.basicAuthEnabled and an authMode setting. The special none mode disables authentication. Another mode, ui_login, adds a JWT-based login integrated with the web UI. The README explains that external readers and desktop clients connect to a running server. Those clients may use API paths that behave differently from the browser session.

Review every access surface

Start with the web UI and then verify the API routes used by the clients. Check whether unauthenticated requests can list sources, read a library entry, start a download, or change configuration. Test a browser session, a Basic-auth request, and a UI-login token according to the configured mode. The presence of a login form does not prove that every endpoint checks the same identity.

If the server is behind a reverse proxy, confirm the proxy does not add authentication to one path while leaving another path exposed. Also check WebSocket or streaming paths if the client uses them, because a proxy may protect HTML but pass upgrade requests directly. The server should have a single documented edge policy and direct access to the application port should be blocked.

Protect the source and download plane

The server fetches content from configured sources and writes downloaded chapters into its data directory. Treat source credentials, cookies, and extension configuration as sensitive. A user who can change source settings may be able to trigger requests from the server network, install an extension, or redirect downloads. Review access to the data and config directories as well as the web UI.

Keep Java and the server distribution current. Back up library state before upgrading, and verify the authentication setting after the upgrade. Configuration keys can be supplied in files or command-line system properties, so a container environment that looks protected may still override authMode at startup.

Validate the title candidate

Use the title as a product marker, then check static assets, API paths, the login response, and version evidence. Do not attempt to access another person's library. The owner should confirm the active authentication mode, accounts, source list, download permissions, and whether the service is intentionally reachable.

The 1,278-title count is neither a count of open servers nor a vulnerability finding. It is a set of candidates for an authenticated review. Record the query, observation time, selected dork, and validation result. For Suwayomi, the most useful inventory field is the actual authentication mode because it determines which client paths accept a credential.

References

Top comments (0)