WsgiDAV: Blind SQL injection in the MySQL provider
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mar10 | wsgidav | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mar10 | Wsgidav |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p6gw-4frg-j7jw | WsgiDAV MySQL provider has a blind SQL injection |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.506% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mar10
Mar10 wsgidav |
|
| Vendors & Products |
Mar10
Mar10 wsgidav |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | WsgiDAV is a generic and extendable WebDAV server based on WSGI. Prior to 4.3.5, the sample MySQLBrowserProvider in wsgidav/samples/mysql_dav_provider.py concatenates the record key parsed from a request URL directly into SQL WHERE clauses. The affected _exists_record_by_primary_key, _get_field_by_primary_key, and _get_record_by_primary_key methods are part of a shipped example provider that is not enabled by default. An attacker who can access a share explicitly configured with this non-default provider can inject SQL through a normal GET request; anonymously exposed read shares permit a status-code oracle and extraction of arbitrary data reachable by the configured MySQL account. This issue is fixed in version 4.3.5. | |
| Title | WsgiDAV: Blind SQL injection in the MySQL provider | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV4_0
|