GHSA-V5WF-JG37-R9M5

Vulnerability from github – Published: 2023-09-21 17:10 – Updated: 2023-09-21 17:10
VLAI
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.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

Severity
10.0 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "crates.io",
        "name": "sqlpage"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.11.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-42454"
  ],
  "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"
  },
  "details": "### Impact\n\nIf\n - you are using a SQLPage version older than v0.11.1 \n - your SQLPage instance is exposed publicly\n - the database connection string is specified in the `sqlpage/sqlpage.json` configuration file (not in an environment variable)\n - the web_root is the current working directory (the default)\n - your database is exposed publicly\n\nthen an attacker could retrieve the database connection information from SQLPage and use it to connect to your database directly.\n\n### Patches\n\nUpgrade to [v0.11.1](https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1) as soon as possible.\n\n### Workarounds\n\nIf you cannot upgrade immediately:\n\n - Using an environment variable instead of the configuration file to specify the database connection string prevents exposing it on vulnerable versions.\n - 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.\n - And in any case, you should generally avoid exposing your database publicly \n\n### References\n\nhttps://github.com/lovasoa/SQLpage/issues/89\n",
  "id": "GHSA-v5wf-jg37-r9m5",
  "modified": "2023-09-21T17:10:06Z",
  "published": "2023-09-21T17:10:06Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-42454"
    },
    {
      "type": "WEB",
      "url": "https://github.com/lovasoa/SQLpage/issues/89"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/lovasoa/SQLpage"
    },
    {
      "type": "WEB",
      "url": "https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "SQLpage vulnerable to public exposure of database credentials"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.