dbcve.org
CommerceApplication · Sap

CVE-2021-42064

CRITICAL · 9.8 CVSS v3.1 Published 2021-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
If configured to use an Oracle database and if a query is created using the flexible search java api with a parameterized "in" clause, SAP Commerce - versions 1905, 2005, 2105, 2011, allows attacker to execute crafted database queries, exposing backend database. The vulnerability is present if the parameterized "in" clause accepts more than 1000 values.

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 confidence

SAP Commerce's flexible search Java API contains an injection vulnerability when configured with Oracle database. If a parameterized 'in' clause accepts more than 1000 values, the Oracle database driver handling triggers a behavior that allows attackers to craft and execute arbitrary database queries, exposing the backend database.

MitigationLimit the number of values accepted in parameterized 'in' clauses to below 1000, implement strict input validation on the flexible search API, or upgrade to a patched SAP Commerce version.

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
CommerceApplication
Affected:= 1905= 2005= 2011= 2105

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. Identify installed SAP Commerce version
    Locate the SAP Commerce version from installation metadata, build configuration, or runtime system information (typically found in version.properties, manifest, or hybris administration console)
    Affected if Version matches 1905, 2005, 2011, or 2105 exactly
  2. Confirm Oracle database is in use
    Review the database connection configuration (local.properties, database configuration files, or datasource settings) to identify the database type
    Affected if The system is configured to use Oracle as the backend database
  3. Determine if flexible search API is utilized
    Inspect application code and configuration for usage of the FlexibleSearchService Java API, particularly any dynamic query construction patterns
    Affected if Flexible search API with parameterized queries is in use
  4. Check for 'in' clause value limitations
    Review application code, filters, or validation logic that handles parameterized 'in' clauses in flexible search queries to see if any limit below 1000 values is enforced
    Affected if No input validation or limit exists on the number of values accepted in 'in' clauses within flexible search queries
  5. Verify runtime accepts large 'in' clause inputs
    If possible, test the flexible search endpoint with a parameterized 'in' clause containing more than 1000 values to observe Oracle driver behavior
    Affected if The system accepts and processes 'in' clauses with more than 1000 values without rejecting or limiting them

The environment is affected if running SAP Commerce versions 1905, 2005, 2011, or 2105 with Oracle database, and the flexible search API accepts more than 1000 values in parameterized 'in' clauses without validation limits.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Limit the number of values accepted in parameterized 'in' clauses to below 1000, implement strict input validation on the flexible search API, or upgrade to a patched SAP Commerce version.

Fix this in Commerce Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-42064 — 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-2021-42064 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