CVE-2022-2422
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDue to improper input validation in the Feathers js library, it is possible to perform a SQL injection attack on the back-end database, in case the feathers-sequelize package is used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA SQL injection vulnerability exists in the Feathers JS library when using the feathers-sequelize package. The vulnerability results from improper input validation, allowing attackers to inject malicious SQL queries through unsanitized user-supplied input that gets incorporated directly into database queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 6.0.0, < 6.3.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if feathers-sequelize is in useCheck your package.json or node_modules for the feathers-sequelize package, or run: npm list feathers-sequelizeAffected if feathers-sequelize is listed as a dependency
-
Check the installed version of feathers-sequelizeRun: npm list feathers-sequelize or cat node_modules/feathers-sequelize/package.json to view the version fieldAffected if The version is >= 6.0.0 and < 6.3.4
-
Verify the application uses the Sequelize adapterCheck your Feathers app configuration files (such as app.js or services setup) for the Sequelize service adapter import and initializationAffected if The app initializes and uses @feathersjs/sequelize with a database connection
-
Identify if raw query execution is usedReview service methods in your codebase that call sequelize.query() or use $ raw operators in query objects, especially where user input flows directlyAffected if Code contains direct SQL query execution paths that accept user-supplied parameters without parameterized binding
You are affected if feathers-sequelize version is >= 6.0.0 and < 6.3.4 and your application passes user input into Sequelize queries without proper sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.3.4
Upgrade to a patched version of feathers-sequelize that implements proper input validation and sanitization, or implement parameterized queries/ORM safeguards as a workaround.
Upgrade to feathers-sequelize version 6.3.4 or later
- 1. Check current installed version of feathers-sequelize using npm list feathers-sequelize or yarn list feathers-sequelize
- 2. Update package.json to specify feathers-sequelize version 6.3.4 or later
- 3. Run npm update feathers-sequelize or yarn upgrade feathers-sequelize to install the fixed version
- 4. Test the application to ensure the upgrade does not break existing functionality
- 5. Verify that SQL injection vulnerabilities are no longer present by reviewing code that uses sequelize adapters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2422 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data