Headline
GHSA-v5wf-jg37-r9m5: SQLpage vulnerable to public exposure of database credentials
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
https://github.com/lovasoa/SQLpage/issues/89
Skip to content
Actions
Automate any workflow
Packages
Host and manage packages
Security
Find and fix vulnerabilities
Codespaces
Instant dev environments
Copilot
Write better code with AI
Code review
Manage code changes
Issues
Plan and track work
Discussions
Collaborate outside of code
GitHub Sponsors
Fund open source developers
* The ReadME Project
GitHub community articles
- Pricing
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-42454
SQLpage vulnerable to public exposure of database credentials
Critical severity GitHub Reviewed Published Sep 18, 2023 in lovasoa/SQLpage • Updated Sep 21, 2023
Package
cargo sqlpage (Rust)
Affected versions
< 0.11.1
Description
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.json configuration 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
lovasoa/SQLpage#89
References
- GHSA-v5wf-jg37-r9m5
- https://nvd.nist.gov/vuln/detail/CVE-2023-42454
- lovasoa/SQLpage#89
- https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1
Published to the GitHub Advisory Database
Sep 21, 2023
Last updated
Sep 21, 2023
Related news
SQLpage is a SQL-only webapp builder. Someone using SQLpage versions prior to 0.11.1, whose SQLpage instance is exposed publicly, with a database connection string specified in the `sqlpage/sqlpage.json` configuration file (not in an environment variable), with the web_root is the current working directory (the default), and with their database exposed publicly, is vulnerable to an attacker retrieving database connection information from SQLPage and using it to connect to their database directly. Version 0.11.0 fixes this issue. Some workarounds are available. 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. One should also avoid exposing one's database publicly.