SQLpage vulnerable to public exposure of database credentials
cve-program · CVE-2023-42454
PublishedSQLpage 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.
Read the publisher's advisoryeuvd · EUVD-2023-2596
PublishedSQLpage 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.
Read the publisher's advisorynvd · CVE-2023-42454
PublishedSQLpage 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.
Read the publisher's advisoryosv · GHSA-v5wf-jg37-r9m5
Published### 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](https://github.com/lovasoa/SQLpage/releases/tag/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](https://github.com/lovasoa/SQLpage/blob/main/configuration.md) (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
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-42454 · CVE overview and exploitation status
cve-program · CVE-2023-42454
- https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5
- https://github.com/lovasoa/SQLpage/issues/89
- https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1
euvd · EUVD-2023-2596
- https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5
- https://github.com/lovasoa/SQLpage/issues/89
- https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1
nvd · CVE-2023-42454
- https://github.com/lovasoa/SQLpage/issues/89
- https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1
- https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5
osv · GHSA-v5wf-jg37-r9m5
Related changes
Linked by CVE identifierNo related changes are available here.