CVE-2022-41204
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 · uneditedAn attacker can change the content of an SAP Commerce - versions 1905, 2005, 2105, 2011, 2205, login page through a manipulated URL. They can inject code that allows them to redirect submissions from the affected login form to their own server. This allows them to steal credentials and hijack accounts. A successful attack could compromise the Confidentiality, Integrity, and Availability of the system.
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 confidenceThis is an open redirect/URL manipulation vulnerability in SAP Commerce login page. Attackers can modify the login page content via crafted URL parameters and inject code that redirects form submissions to attacker-controlled servers, enabling credential theft and session hijacking.
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= 1905= 2005= 2011= 2105= 2205CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installed SAP Commerce versionCheck the version file or system information: Look for version.info, local.properties, or use SAP Commerce admin console to view system information. Common path: $HYBRIS_HOME/hybris/bin/platform/build.number or check the installer properties.Affected if Installed version is exactly 1905, 2005, 2011, 2105, or 2205
-
Verify login page is accessibleAccess the storefront login URL (typically /login or /auth in your SAP Commerce instance). Confirm the page loads and accepts user input.Affected if Login page is exposed and functional without additional authentication
-
Check for vulnerable URL parameter handlingInspect the login form HTML source. Look at the form action attribute. Try appending a test parameter like ?redirectUrl=http://example.com to the login URL and check if it influences the form action or creates a redirect.Affected if URL parameters can modify the form action or create redirects without sanitization
-
Review login controller configurationLocate the login controller source code or configuration. Check the Spring MVC configuration files for the login flow, typically in web/webroot/WEB-INF/config or in the accelerator extensions under the /web/src folder.Affected if Login controller accepts and processes redirect/URL parameters without validation
Your environment is affected if you run SAP Commerce version 1905, 2005, 2011, 2105, or 2205 and the login page is accessible with unvalidated URL parameters influencing redirects or form actions.
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 · scopedApply the relevant SAP security patch for CVE-2022-41204 and implement strict validation/sanitization of all URL parameters and form action attributes in the login flow.
SAP Commerce 2205 or later (includes fix for CVE-2022-41204)
- Check SAP Security Note 3268709 for the specific patch/solution for this vulnerability
- Review the SAP Commerce version compatibility matrix to determine upgrade eligibility
- Plan upgrade to SAP Commerce 2205 or later which contains the security fix
- Test the upgrade in a non-production environment first
- Apply the upgrade to production after successful testing
- Verify the open redirect vulnerability is resolved by testing the login page URL manipulation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41204 — 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-41204 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