GHSA-v5wf-jg37-r9m5
Suggest an improvement- Source
- https://github.com/advisories/GHSA-v5wf-jg37-r9m5
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/09/GHSA-v5wf-jg37-r9m5/GHSA-v5wf-jg37-r9m5.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-v5wf-jg37-r9m5
- Aliases
- Published
- 2023-09-21T17:10:06Z
- Modified
- 2026-09-10T03:50:03Z
- Severity
-
- 10.0 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N CVSS Calculator
- Summary
- SQLpage vulnerable to public exposure of database credentials
- Details
-
Impact
If
- you are using a SQLPage version older than v0.11.1
- your SQLPage instance is exposed publicly
- the database connection string is specified in the
sqlpage/sqlpage.jsonconfiguration file (not in an environment variable) - the web_root is the current working directory (the default)
- your database is exposed publicly
then an attacker could retrieve the database connection information from SQLPage and use it to connect to your database directly.
Patches
Upgrade to v0.11.1 as soon as possible.
Workarounds
If you cannot upgrade immediately:
- Using an environment variable instead of the configuration file to specify the database connection string prevents exposing it on vulnerable versions.
- Using a different web root (that is not a parent of the SQLPage configuration directory) fixes the issue.
- And in any case, you should generally avoid exposing your database publicly
References
- Database specific
{ "cwe_ids": [ "CWE-200" ], "github_reviewed": true, "github_reviewed_at": "2023-09-21T17:10:06Z", "nvd_published_at": "2023-09-18T22:15:47Z", "severity": "CRITICAL" }- References
Affected packages
crates.io / sqlpage
Package
- Name
- sqlpage
- View open source insights on deps.dev
- Purl
- pkg:cargo/sqlpage