Datasette is an open source multi-tool for exploring and publishing data. This bug affects Datasette instances running a Datasette 1.0 alpha - 1.0a0, 1.0a1, 1.0a2 or 1.0a3 - in an online accessible location but with authentication enabled using a plugin such as datasette-auth-passwords. The /-/api API explorer endpoint could reveal the names of both databases and tables - but not their contents - to an unauthenticated user. Datasette 1.0a4 has a fix for this issue. This will block access to the API explorer but will still allow access to the Datasette read or write JSON APIs, as those use different URL patterns within the Datasette /database hierarchy. This issue is patched in version 1.0a4.
The product’s intended functionality exposes information to certain actors in accordance with the developer’s security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product’s administrator, users, or others whose information is being processed.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Datasette | Datasette | 1.0-alpha0 (including) | 1.0-alpha0 (including) |
| Datasette | Datasette | 1.0-alpha1 (including) | 1.0-alpha1 (including) |
| Datasette | Datasette | 1.0-alpha2 (including) | 1.0-alpha2 (including) |
| Datasette | Datasette | 1.0-alpha3 (including) | 1.0-alpha3 (including) |
When handling information, the developer must consider whether the information is regarded as sensitive by different stakeholders, such as users or administrators. Each stakeholder effectively has its own intended security policy that the product is expected to uphold. When a developer does not treat that information as sensitive, this can introduce a vulnerability that violates the expectations of the product’s users.