dbcve.org
Feathers SequelizeApplication · Feathersjs

CVE-2022-29823

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-26
Fix available
A fix is available. Upgrade to 6.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Feather-Sequalize cleanQuery method uses insecure recursive logic to filter unsupported keys from the query object. This results in a Remote Code Execution (RCE) with privileges of application.

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 confidence

The Feather-Sequelize library contains a cleanQuery method that uses insecure recursive logic to filter unsupported keys from query objects. This flawed filtering allows attackers to inject malicious payloads that bypass the filter, ultimately achieving remote code execution with the privileges of the application process.

MitigationUpdate to a patched version of Feather-Sequelize if available; otherwise, implement input validation and sanitization at the application layer or deploy a WAF to block malicious query patterns until the library can be updated.

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
Feathers SequelizeApplication
Affected:>= 6.0.0, < 6.3.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed feather-sequelize package version
    Run 'npm list feather-sequelize' or check package.json to see the installed version of the feather-sequelize package
    Affected if Version is >= 6.0.0 and < 6.3.4
  2. Identify cleanQuery method usage in codebase
    Search the codebase for occurrences of 'cleanQuery' - this method is used to filter unsupported keys from query objects in service adapters
    Affected if The cleanQuery method is present and used in the application code
  3. Verify if query parameters come from user input
    Inspect the service files that use Sequelize adapters and check if req.query, URL parameters, or HTTP request bodies are passed to query filtering logic
    Affected if User-controlled input from HTTP requests flows into the query object processed by cleanQuery
  4. Confirm application uses affected feathers-sequelize adapter
    Check if the application initializes a Feathers service with @feathersjs/sequelize adapter and uses query filtering
    Affected if The application uses @feathersjs/sequelize adapter with query parameter handling enabled

A user is affected if they have feather-sequelize version 6.0.0 through 6.3.4 and their application passes user-supplied query parameters to the cleanQuery method, allowing malicious payload injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.3.4 or later
Fixed in 6.3.4
Interim mitigation

Update to a patched version of Feather-Sequelize if available; otherwise, implement input validation and sanitization at the application layer or deploy a WAF to block malicious query patterns until the library can be updated.

Recommended fix High confidence

Upgrade to feathers-sequelize version 6.3.4 or later

  1. Check current version of feathers-sequelize in package.json
  2. Update the version requirement in package.json to ^6.3.4 or later (e.g., "feathers-sequelize": "^6.3.4")
  3. Run 'npm install' or 'yarn install' to install the updated package
  4. Verify the installed version is >= 6.3.4
  5. Test the application to ensure the cleanQuery functionality still works correctly
  6. Deploy the updated application
Caveat Review the changelog between your current version and 6.3.4 for any breaking changes; however, this is a security patch release with minimal expected impact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Feathers Sequelize Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29823 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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