CVE-2016-1000225 json
SQL Injection via GeoJSON in sequelize
published 6y ago modified 3y ago also GHSA-5v9h-q3gj-c32x
- cvss
- 9.8
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Affected versions of `sequelize` are vulnerable to SQL Injection in Models that have fields with the `GEOMETRY` DataType. This vulnerability occurs because single quotes in document values are not escaped for GeoJSON documents using `ST_GeomFromGeoJSON`, and MySQL GeoJSON documents using `GeomFromText`.
## Recommendation
Update to version 3.23.6 or later.
Patch / fix
- npm sequelize 3.23.6
- github.com/sequelize/sequelize@14e3dea commit
- github.com/sequelize/sequelize@18ac910 commit
- github.com/sequelize/sequelize@562d525 commit
- github.com/sequelize/sequelize@f93af43 commit
- github.com/sequelize/sequelize#6302 pull request
- github.com/sequelize/sequelize#6306 pull request
Is CVE-2016-1000225 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | sequelize | >=3.4.0, <3.23.6 |
3.23.6 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/sequelize/sequelize/pull/6302
web
-
github.com
/sequelize/sequelize/pull/6306
web
-
github.com
/sequelize/sequelize/commit/14e3deaf3ad27f12900e5275db1d448844c9de3e
web
-
github.com
/sequelize/sequelize/commit/18ac91040d9c57351d26ba998f460e214255b704
web
-
github.com
/sequelize/sequelize/commit/562d52585902090f4e53eb21c61314098c29d795
web
-
github.com
/sequelize/sequelize/commit/f93af43a1d86400487f5e3d9762f1a4b7cf6b1e1
web
-
nvd.nist.gov
/vuln/detail/CVE-2016-1000225
advisory
-
github.com
/sequelize/sequelize/issues/6194
web
-
github.com
/sequelize/sequelize
package
-
snyk.io
/vuln/npm:sequelize:20160718
web
Sources
- GitHub Advisory GHSA-5v9h-q3gj-c32x
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.