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.
| Score | Percentile |
|---|---|
| 0.33% | 55.55% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 5.3 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-7ch3-7pp7-7cpq ↗ |
| CVE | CVE-2023-40570 ↗ |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| pip | datasette | >= 1.0a0, < 1.0a4 | 1.0a4 | — |