Spring Data MongodbDatabase / datastore · VMware
CVE-2022-22980
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 · uneditedA Spring Data MongoDB application is vulnerable to SpEL Injection when using @Query or @Aggregation-annotated query methods with SpEL expressions that contain query parameter placeholders for value binding if the input is not sanitized.
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 · high confidenceA Spring Data MongoDB application is vulnerable to SpEL injection when using @Query or @Aggregation-annotated query methods with SpEL expressions containing query parameter placeholders for value binding without proper input sanitization. An unauthenticated attacker can inject malicious SpEL expressions through query parameters to achieve arbitrary code execution.
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
Spring Data MongodbDatabase / datastore
<= 3.3.4= 3.4.0CVSS 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 Spring Data MongoDB dependency versionCheck your project dependency management (Maven pom.xml, Gradle build.gradle, or JAR manifest) for 'spring-data-mongodb' versionAffected if Version is 3.4.0 or <= 3.3.4
-
Locate @Query annotated repository methodsSearch codebase for '@Query' annotations in any Java interface annotated with @Repository or extending MongoRepositoryAffected if @Query annotations contain SpEL expressions like '#{' and use user-supplied parameter values
-
Locate @Aggregation annotated repository methodsSearch codebase for '@Aggregation' annotations in MongoDB repository interfacesAffected if @Aggregation annotations contain SpEL expressions like '#{' that incorporate method parameters
-
Identify SpEL parameter placeholder usageExamine @Query and @Aggregation SpEL expressions for parameter placeholders such as '#paramName' that bind directly to method arguments without sanitizationAffected if SpEL expressions reference method parameters that could be user-controlled input without sanitization or proper parameter binding
Your environment is affected if Spring Data MongoDB version is 3.4.0 or <= 3.3.4 AND your codebase uses @Query or @Aggregation annotations with SpEL expressions that incorporate user-controlled parameters.
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 · scopedUpgrade to Spring Data MongoDB 3.4.0+ or 3.3.4+, and sanitize all user input used in SpEL expressions within @Query or @Aggregation annotations, or use parameter binding instead of SpEL where possible.
Spring Data MongoDB 3.4.1 or later (3.x branch) / 4.x latest
- 1. Identify the current Spring Data MongoDB version in your project's pom.xml or build.gradle file
- 2. Upgrade Spring Data MongoDB to version 3.4.1 or later (if using 3.x branch)
- 3. Alternatively, upgrade to the latest 4.x release for the most recent security fixes
- 4. Rebuild and test the application to ensure no regressions occur with the upgraded dependency
- 5. Verify that @Query and @Aggregation annotated methods with SpEL do not accept unsanitized user input
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Data Mongodb
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22980 — 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-22980 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