Filtered by vendor Sequelizejs
Subscribe
Total
12 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2023-22578 | 1 Sequelizejs | 1 Sequelize | 2023-03-03 | N/A | 9.8 CRITICAL |
| Due to improper artibute filtering in the sequalize js library, can a attacker peform SQL injections. | |||||
| CVE-2023-25813 | 1 Sequelizejs | 1 Sequelize | 2023-03-02 | N/A | 9.8 CRITICAL |
| Sequelize is a Node.js ORM tool. In versions prior to 6.19.1 a SQL injection exploit exists related to replacements. Parameters which are passed through replacements are not properly escaped which can lead to arbitrary SQL injection depending on the specific queries in use. The issue has been fixed in Sequelize 6.19.1. Users are advised to upgrade. Users unable to upgrade should not use the `replacements` and the `where` option in the same query. | |||||
| CVE-2023-22580 | 1 Sequelizejs | 1 Sequelize | 2023-02-24 | N/A | 7.5 HIGH |
| Due to improper input filtering in the sequalize js library, can malicious queries lead to sensitive information disclosure. | |||||
| CVE-2023-22579 | 1 Sequelizejs | 1 Sequelize | 2023-02-24 | N/A | 8.8 HIGH |
| Due to improper parameter filtering in the sequalize js library, can a attacker peform injection. | |||||
| CVE-2019-10748 | 1 Sequelizejs | 1 Sequelize | 2019-10-30 | 7.5 HIGH | 9.8 CRITICAL |
| Sequelize all versions prior to 3.35.1, 4.44.3, and 5.8.11 are vulnerable to SQL Injection due to JSON path keys not being properly escaped for the MySQL/MariaDB dialects. | |||||
| CVE-2019-10749 | 1 Sequelizejs | 1 Sequelize | 2019-10-30 | 7.5 HIGH | 9.8 CRITICAL |
| sequelize before version 3.35.1 allows attackers to perform a SQL Injection due to the JSON path keys not being properly sanitized in the Postgres dialect. | |||||
| CVE-2019-10752 | 1 Sequelizejs | 1 Sequelize | 2019-10-21 | 7.5 HIGH | 9.8 CRITICAL |
| Sequelize, all versions prior to version 4.44.3 and 5.15.1, is vulnerable to SQL Injection due to sequelize.json() helper function not escaping values properly when formatting sub paths for JSON queries for MySQL, MariaDB and SQLite. | |||||
| CVE-2016-10550 | 1 Sequelizejs | 1 Sequelize | 2019-10-09 | 7.5 HIGH | 9.8 CRITICAL |
| sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS If user input goes into the `limit` or `order` parameters, a malicious user can put in their own SQL statements. This affects sequelize 3.16.0 and earlier. | |||||
| CVE-2016-10556 | 1 Sequelizejs | 1 Sequelize | 2019-10-09 | 5.0 MEDIUM | 7.5 HIGH |
| sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS In Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped. This causes potential SQL injection in sequelize 3.19.3 and earlier, where a malicious user could put `["test", "'); DELETE TestTable WHERE Id = 1 --')"]` inside of ``` database.query('SELECT * FROM TestTable WHERE Name IN (:names)', { replacements: { names: directCopyOfUserInput } }); ``` and cause the SQL statement to become `SELECT Id FROM Table WHERE Name IN ('test', '\'); DELETE TestTable WHERE Id = 1 --')`. In Postgres, MSSQL, and SQLite, the backslash has no special meaning. This causes the the statement to delete whichever Id has a value of 1 in the TestTable table. | |||||
| CVE-2016-10554 | 1 Sequelizejs | 1 Sequelize | 2019-10-09 | 7.5 HIGH | 9.8 CRITICAL |
| sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS. Before version 1.7.0-alpha3, sequelize defaulted SQLite to use MySQL backslash escaping, even though SQLite uses Postgres escaping. | |||||
| CVE-2016-10553 | 1 Sequelizejs | 1 Sequelize | 2019-10-09 | 7.5 HIGH | 9.8 CRITICAL |
| sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS. A fix was pushed out that fixed potential SQL injection in sequelize 2.1.3 and earlier. | |||||
| CVE-2019-11069 | 1 Sequelizejs | 1 Sequelize | 2019-04-22 | 5.0 MEDIUM | 7.5 HIGH |
| Sequelize version 5 before 5.3.0 does not properly ensure that standard conforming strings are used. | |||||