Vulnerability-Lookup

GHSA-V5WF-JG37-R9M5

Vulnerability from github – Published: 2023-09-21 17:10 – Updated: 2023-09-21 17:10

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

JSON

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"
}

CVE-2023-42454 (GCVE-0-2023-42454)

Vulnerability from cvelistv5 – Published: 2023-09-18 21:36 – Updated: 2024-09-26 13:38

Title

SQLpage vulnerable to public exposure of database credentials

Summary

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.

Severity

10 (Critical)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

SSVC

Exploitation: none Automatable: yes Technical Impact: total

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2024-09-26 13:34 UTC

CWE

CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor

Assigner

GitHub_M CNA under the mitre root

CNA scorecard C 72/100 over 7886 records in the last 180 days details

References

3 references

URL	Tags
https://github.com/lovasoa/SQLpage/security/advis…	x_refsource_CONFIRM
https://github.com/lovasoa/SQLpage/issues/89	x_refsource_MISC
https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1	x_refsource_MISC

Impacted products

2 products

Vendor	Product	Version
lovasoa	SQLpage	Affected: < 0.11.1
lovasoa	sqlpage	Affected: 0 , < 0.11.1 (custom) cpe:2.3:a:lovasoa:sqlpage::::::::

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T19:23:38.759Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5",
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5"
          },
          {
            "name": "https://github.com/lovasoa/SQLpage/issues/89",
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/lovasoa/SQLpage/issues/89"
          },
          {
            "name": "https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1",
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "affected": [
          {
            "cpes": [
              "cpe:2.3:a:lovasoa:sqlpage:*:*:*:*:*:*:*:*"
            ],
            "defaultStatus": "unknown",
            "product": "sqlpage",
            "vendor": "lovasoa",
            "versions": [
              {
                "lessThan": "0.11.1",
                "status": "affected",
                "version": "0",
                "versionType": "custom"
              }
            ]
          }
        ],
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-42454",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-26T13:34:43.255712Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-26T13:38:53.969Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "SQLpage",
          "vendor": "lovasoa",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.11.1"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s database publicly."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 10,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-09-18T21:36:02.842Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/lovasoa/SQLpage/security/advisories/GHSA-v5wf-jg37-r9m5"
        },
        {
          "name": "https://github.com/lovasoa/SQLpage/issues/89",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/lovasoa/SQLpage/issues/89"
        },
        {
          "name": "https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/lovasoa/SQLpage/releases/tag/v0.11.1"
        }
      ],
      "source": {
        "advisory": "GHSA-v5wf-jg37-r9m5",
        "discovery": "UNKNOWN"
      },
      "title": "SQLpage vulnerable to public exposure of database credentials"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2023-42454",
    "datePublished": "2023-09-18T21:36:02.842Z",
    "dateReserved": "2023-09-08T20:57:45.574Z",
    "dateUpdated": "2024-09-26T13:38:53.969Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

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.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted

GHSA-V5WF-JG37-R9M5

Impact

Patches

Workarounds

References

CVE-2023-42454 (GCVE-0-2023-42454)

Tags

Sightings

Nomenclature

Vulnerability timeline

Related by attack behaviour