An open API service providing security vulnerability metadata for many open source software ecosystems.

GSA_kwCzR0hTQS12NXdmLWpnMzctcjltNc4AA1_y

Critical EPSS: 0.00101% (0.29109 Percentile) EPSS:

SQLpage vulnerable to public exposure of database credentials

Affected Packages Affected Versions Fixed Versions
cargo:sqlpage < 0.11.1 0.11.1
0 Dependent packages
0 Dependent repositories
54,032 Downloads total

Affected Version Ranges

All affected versions

0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.4.1, 0.4.4, 0.5.3, 0.6.6, 0.6.7, 0.6.10

All unaffected versions

0.14.0, 0.15.0, 0.15.1, 0.15.2, 0.16.0, 0.16.1, 0.17.0, 0.17.1, 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1, 0.20.0, 0.20.1, 0.20.2, 0.20.3, 0.20.4, 0.20.5, 0.21.0, 0.22.0, 0.23.0, 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.26.2, 0.27.0, 0.28.0, 0.29.0, 0.30.0, 0.30.1, 0.31.0, 0.32.0, 0.32.1, 0.33.0, 0.33.1, 0.34.0, 0.35.0, 0.35.1, 0.35.2

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

https://github.com/lovasoa/SQLpage/issues/89

References: