Skip to content

SQLpage vulnerable to public exposure of database credentials

Critical severity GitHub Reviewed Published Sep 18, 2023 in sqlpage/SQLPage • Updated Nov 12, 2023

Package

cargo sqlpage (Rust)

Affected versions

< 0.11.1

Patched 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

sqlpage/SQLPage#89

References

@lovasoa lovasoa published to sqlpage/SQLPage Sep 18, 2023
Published by the National Vulnerability Database Sep 18, 2023
Published to the GitHub Advisory Database Sep 21, 2023
Reviewed Sep 21, 2023
Last updated Nov 12, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

EPSS score

0.140%
(51st percentile)

Weaknesses

CVE ID

CVE-2023-42454

GHSA ID

GHSA-v5wf-jg37-r9m5

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.