DEV Community

SorrelThorncroft
SorrelThorncroft

Posted on

Flatnotes has 442 title matches; its authentication mode is the first question

Flatnotes has 442 title matches; its authentication mode is the first question

Flatnotes is a self-hosted note application that stores Markdown files in a flat directory rather than a database. That design makes the filesystem path part of the application's security model. A count-only ZoomEye probe found 442 assets with title="Flatnotes" and zero with app="Flatnotes". The title count identifies candidates for review. It does not show which authentication mode each deployment uses.

Flatnotes says the application supports multiple authentication options: none, read-only, username and password, and two-factor authentication. The environment-variable documentation also describes the first-run QR code used to enroll an authenticator application. These options make a generic product count insufficient. A deployment that presents a login page may still be configured with a different access mode than another instance.

The ZoomEye evidence

The SDK queried app="Flatnotes" and title="Flatnotes" with sub_type="all", page 1, and page size 1 at 08:43 Asia/Shanghai on 17 November 2026. The app query returned 0 and the title query returned 442. ZoomEye's total is attached to the exact query; the page size only limits returned records. A matching title can be a note interface, a login page, or a page generated by a related deployment.

Because the product has no application match in this bounded probe, analysts should not infer a clean inventory from the zero. Confirm the response, the login behavior, and the file-store owner. A CVE search or an unrelated technology name is not a substitute for identifying Flatnotes itself.

Authentication controls the note boundary

Start with the effective mode. If authentication is disabled, the service should not be reachable by untrusted networks. If read-only mode is enabled, verify that every write route, upload path, and administrative action is actually blocked. Username and password mode needs secret handling, account recovery, and a plan for removal. Two-factor enrollment should be tied to the correct user and recoverable through a controlled process.

The flat-file model also needs host controls. The process user should read only the note directory it needs. The directory should not be shared with unrelated web applications, and backups should preserve ownership and permissions. If the notes are stored on a network filesystem, review UID mapping, mount attributes, and snapshot visibility as part of the same exposure.

What ZoomEye adds

A public count helps an owner find unmanaged instances and decide which hosts are reachable at all. The next step is a short validation record: hostname, owner, authentication mode, TLS status, write capability, and the last intentional deployment change. For a service that holds personal notes, a title match is only a lead until these fields are known.

References

Top comments (0)