GHSA-8c25-f3mj-v6h8 CVE-2023-22580
Sequelize information disclosure vulnerability
- Severity
- 5.3 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.58%
- Chance of exploitation in the next 30 days. Higher than 47.83% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
- Available
- 2 packages have a fixed version
Description
Due to improper input filtering in the sequelize js library, can malicious queries lead to sensitive information disclosure.
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| @sequelize/core | < 7.0.0-alpha.20 |
7.0.0-alpha.20 |
| sequelize | < 6.28.1 |
6.28.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
@sequelize/core npm → 7.0.0-alpha.20
- npm
npm install @sequelize/core@7.0.0-alpha.20- yarn
yarn add @sequelize/core@7.0.0-alpha.20- pnpm
pnpm add @sequelize/core@7.0.0-alpha.20
sequelize npm → 6.28.1
- npm
npm install sequelize@6.28.1- yarn
yarn add sequelize@6.28.1- pnpm
pnpm add sequelize@6.28.1
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-v8fg-2rw7-q452 Sequelize: SQL Injection (Oracle DB) | Critical | Also affects sequelize |
| GHSA-6457-6jrx-69cr Sequelize v6 Vulnerable to SQL Injection via JSON Column Cast Type | High | Also affects sequelize |
| GHSA-wrh9-cjv3-2hpw Sequelize vulnerable to SQL Injection via replacements | Critical | Also affects sequelize |
| GHSA-vqfx-gj96-3w95 Unsafe fall-through in getWhereConditions | High | Also affects sequelize |
| GHSA-f598-mfpv-gmfx Sequelize - Default support for “raw attributes” when using parentheses | Critical | Also affects sequelize |
| GHSA-fw4p-36j9-rrj3 Denial of Service in sequelize | Medium | Also affects sequelize |
| GHSA-5v9h-q3gj-c32x SQL Injection via GeoJSON in sequelize | Critical | Also affects sequelize |
| GHSA-2598-2f59-rmhq SQL Injection in sequelize | Critical | Also affects sequelize |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor