GHSA-XQH8-5J36-4556

Vulnerability from github – Published: 2019-08-26 16:59 – Updated: 2022-06-15 18:39
VLAI?
Summary
SQL Injection in connect-pg-simple
Details

Impact

An unlikely SQL injection if the case of an unsanitized table name input.

Patches

The user should upgrade to 6.0.1. Due to its low impact a backport has not been made to the 5.x branch.

Workarounds

If there is no likelihood that the tableName or schemaName options sent to the constructor could be of an unsanitized nature, then no workaround is needed. Else the input could be sanitized and escaped before sending it in. Take note though that such an escaping would need to be removed when upgrading to 6.0.1 or later, to avoid double escaping.

References

For more information

If you have any questions or comments about this advisory: * Open an issue in voxpelli/node-connect-pg-simple * Email maintainer at pelle@kodfabrik.se

Severity ?
7.3 (High)
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "connect-pg-simple"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2019-15658"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T22:04:11Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\nAn unlikely SQL injection if the case of an unsanitized table name input.\n\n### Patches\nThe user should upgrade to `6.0.1`. Due to its low impact a backport has not been made to the `5.x` branch.\n\n### Workarounds\nIf there is no likelihood that the `tableName` or `schemaName` options sent to the constructor could be of an unsanitized nature, then no workaround is needed. Else the input could be sanitized and escaped before sending it in. Take note though that such an escaping would need to be removed when upgrading to `6.0.1` or later, to avoid double escaping.\n\n### References\n* [Security issue disclosure](https://github.com/voxpelli/node-connect-pg-simple/issues/151)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [voxpelli/node-connect-pg-simple](https://github.com/voxpelli/node-connect-pg-simple)\n* Email maintainer at [pelle@kodfabrik.se](mailto:pelle@kodfabrik.se)\n",
  "id": "GHSA-xqh8-5j36-4556",
  "modified": "2022-06-15T18:39:04Z",
  "published": "2019-08-26T16:59:45Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/voxpelli/node-connect-pg-simple/security/advisories/GHSA-xqh8-5j36-4556"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-15658"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-xqh8-5j36-4556"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/voxpelli/node-connect-pg-simple"
    },
    {
      "type": "WEB",
      "url": "https://snyk.io/vuln/SNYK-JS-CONNECTPGSIMPLE-460154"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/1153"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "SQL Injection in connect-pg-simple"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.