dbcve.org
Commerce CloudApplication · Sap

CVE-2021-21445

MEDIUM · 5.4 CVSS v3.1 Published 2021-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
SAP Commerce Cloud, versions - 1808, 1811, 1905, 2005, 2011, allows an authenticated attacker to include invalidated data in the HTTP response Content Type header, due to improper input validation, and sent to a Web user. A successful exploitation of this vulnerability may lead to advanced attacks, including cross-site scripting and page hijacking.

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

This is a Content-Type header injection vulnerability in SAP Commerce Cloud where an authenticated attacker can manipulate the HTTP response Content-Type header due to improper input validation. This allows the attacker to potentially smuggle malicious content past security filters by controlling the MIME type the browser interprets, leading to cross-site scripting and page hijacking attacks.

MitigationImplement strict input validation on all values used to set HTTP headers, particularly the Content-Type header. Additionally, set the X-Content-Type-Options: nosniff header to prevent MIME-type sniffing by browsers.

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
Commerce CloudApplication
Affected:= 1808= 1811= 1905= 2005= 2011

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 if SAP Commerce Cloud is installed
    Check for SAP Commerce Cloud installation by looking for the 'hybris' directory structure, the 'platform' folder, or the 'hybris/bin/platform' path. Alternatively, check for the 'yaccelerator' extension or search for 'hybris' in running process names.
    Affected if The system does not run SAP Commerce Cloud - this CVE does not apply.
  2. Determine the installed SAP Commerce Cloud version
    Look for the version file typically located at <hybris_installation>/bin/platform/build.number, or check the 'installer.properties' or 'version.info' files in the hybris home directory. You may also check the 'about' page in the administration console if accessible.
    Affected if The installed version matches 1808, 1811, 1905, 2005, or 2011 exactly.
  3. Verify if Content-Type header manipulation is possible
    As an authenticated user, test if you can influence the Content-Type header in HTTP responses. This typically requires code review or access to backend configuration. Check whether user-supplied input (such as file upload names or accept headers) is used to set the Content-Type response header without validation.
    Affected if User-controlled input can influence the Content-Type header in responses.
  4. Check if X-Content-Type-Options header is configured
    Inspect HTTP responses from the application using browser developer tools or a proxy (Burp Suite, OWASP ZAP). Look for the 'X-Content-Type-Options' header in the response headers.
    Affected if The X-Content-Type-Options header is missing or set to a value other than 'nosniff', indicating the mitigation is not applied.

A user is affected if they run SAP Commerce Cloud versions 1808, 1811, 1905, 2005, or 2011 and the application allows user input to influence the Content-Type header without the X-Content-Type-Options: nosniff mitigation in place.

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

Implement strict input validation on all values used to set HTTP headers, particularly the Content-Type header. Additionally, set the X-Content-Type-Options: nosniff header to prevent MIME-type sniffing by browsers.

Fix this in Commerce Cloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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