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.
To work around this issue, block all traffic to the /-/api
endpoint. This can be done with a proxy such as Apache or NGINX, or by installing the datasette-block plugin and adding the following configuration to your metadata.json
or metadata.yml
file:
{
"plugins": {
"datasette-block": {
"prefixes": ["/-/api"]
}
}
}
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.
{ "nvd_published_at": "2023-08-25T01:15:09Z", "cwe_ids": [ "CWE-200", "CWE-213" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2023-08-22T18:06:46Z" }