dbcve.org
Commerce CloudApplication · Sap

CVE-2024-33003

CRITICAL · 9.1 CVSS v3.1 Published 2024-08-13
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
Some OCC API endpoints in SAP Commerce Cloud allows Personally Identifiable Information (PII) data, such as passwords, email addresses, mobile numbers, coupon codes, and voucher codes, to be included in the request URL as query or path parameters. On successful exploitation, this could lead to a High impact on confidentiality and integrity of the 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 · high confidence

SAP Commerce Cloud OCC (Omnichannel Commerce) API endpoints improperly transmit Personally Identifiable Information (PII) including passwords, email addresses, mobile numbers, coupon codes, and voucher codes as URL query or path parameters instead of using more secure request body or header mechanisms. This exposes sensitive data in server logs, browser history, proxies, and cached data.

MitigationRestructure affected OCC API endpoints to receive PII via request body (POST/PUT) or secure headers instead of URL parameters; implement logging filters to strip sensitive parameters; audit and update all APIs handling PII.

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:= 1811= 1905= 2005= 2011= 2105= 2205= com_cloud_2211= hy_com_1808

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Verify SAP Commerce Cloud version
    Check the installed SAP Commerce Cloud version in the system information or license details. Common locations: SAP Hybris Administration Console ( HAC ) > Platform > Version, or check the manifest/version files in the installation directory.
    Affected if The installed version matches 1811, 1905, 2005, 2011, 2105, 2205, com_cloud_2211, or hy_com_1808 exactly.
  2. Identify exposed OCC API endpoints
    Review the exposed REST endpoints in your SAP Commerce Cloud environment. Check the OCC (Omnichannel Commerce) layer configuration files such as occwebservices-web-spring.xml or the API endpoint definitions in the backoffice/Admin Console.
    Affected if OCC API endpoints are publicly accessible or exposed to untrusted networks.
  3. Inspect server access logs for PII in URL parameters
    Examine web server logs (e.g., Apache, Tomcat, or SAP Commerce Cloud server logs) for requests to OCC endpoints. Look for patterns where email addresses, phone numbers, coupon codes, or voucher codes appear as query string parameters in the URL.
    Affected if Server logs contain URLs with sensitive data like passwords, email addresses, mobile numbers, coupon codes, or voucher codes in query parameters.
  4. Review API request/response configurations
    Inspect the OCC API controller configurations or Spring XML definitions to verify how sensitive parameters are being received. Check controllers for @RequestParam annotations on fields containing PII.
    Affected if OCC API controllers are configured to receive sensitive fields (email, mobile, password, coupon, voucher) via @RequestParam (URL query/path parameters) rather than @RequestBody or headers.
  5. Audit network traces or API gateway logs
    Capture or review network traffic/API gateway logs for OCC API calls. Look for GET requests or URL-based API calls that include PII in the URL path or query string.
    Affected if Live or captured API traffic shows PII transmitted as URL query parameters rather than in request body (POST/PUT) or headers.

A user is affected if they run a vulnerable SAP Commerce Cloud version AND have OCC API endpoints accessible while PII data appears in URL parameters rather than request bodies or secure headers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restructure affected OCC API endpoints to receive PII via request body (POST/PUT) or secure headers instead of URL parameters; implement logging filters to strip sensitive parameters; audit and update all APIs handling PII.

Recommended fix Moderate confidence

Latest stable SAP Commerce Cloud release (post-2011)

  1. Identify the current SAP Commerce Cloud version in use by checking the installed product version
  2. Review all OCC (Omnichannel Commerce) API endpoints in the application to identify any that transmit PII (passwords, email addresses, mobile numbers, coupon codes, voucher codes) as query or path parameters
  3. Upgrade to the latest available SAP Commerce Cloud version that includes the security fix for CVE-2024-33003
  4. After upgrade, verify that PII data is no longer transmitted via URL parameters and is instead sent via request body or headers
  5. Review application logs to confirm no PII data is being logged in URL parameters
Caveat Review SAP Commerce Cloud release notes for potential breaking changes between versions when upgrading

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

Fix this in Commerce Cloud Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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