ghsa-2v7q-2xqx-f4q5
Vulnerability from github
Published
2019-02-18 23:54
Modified
2020-08-31 18:11
Summary
Potential SQL Injection in sequelize
Details

Affected versions of sequelize are vulnerable to SQL Injection when user input is passed into findOne or into a statement such as where: "user input".

Recommendation

Update to version 3.0.0 or later.

Version 3.0.0 will introduce a number of breaking changes. Thankfully, the project authors have provided a 2.x -> 3.x upgrade guide to ease this transition.

If upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of where: "input" and findOne("input") are properly sanitized, such as by the use of a wrapper function.

Show details on source website


{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2.1.3"
      },
      "package": {
        "ecosystem": "npm",
        "name": "sequelize"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2016-10553"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T20:53:00Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "Affected versions of `sequelize` are vulnerable to SQL Injection when user input is passed into `findOne` or into a statement such as `where: \"user input\"`.\n\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or later.\n\nVersion 3.0.0 will introduce a number of breaking changes.\nThankfully, the project authors have provided a 2.x -\u003e 3.x [upgrade guide](https://github.com/sequelize/sequelize/wiki/Upgrade-from-2.0-to-3.0) to ease this transition.\n\nIf upgrading is not an option, it is also possible to mitigate this by ensuring that all uses of `where: \"input\"` and `findOne(\"input\")` are properly sanitized, such as by the use of a wrapper function.",
  "id": "GHSA-2v7q-2xqx-f4q5",
  "modified": "2020-08-31T18:11:09Z",
  "published": "2019-02-18T23:54:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-10553"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-2v7q-2xqx-f4q5"
    },
    {
      "type": "WEB",
      "url": "https://github.com/sequelize/sequelize/blob/master/changelog.md#300"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/109"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Potential SQL Injection in sequelize"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…