CVE-2023-37486
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 · uneditedUnder certain conditions SAP Commerce (OCC API) - versions HY_COM 2105, HY_COM 2205, COM_CLOUD 2211, endpoints allow an attacker to access information which would otherwise be restricted. On successful exploitation there could be a high impact on confidentiality with no impact on integrity and availability 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 · moderate confidenceSAP Commerce OCC (Omni Commerce Connect) API endpoints in versions HY_COM 2105, HY_COM 2205, and COM_CLOUD 2211 contain an information disclosure vulnerability where certain conditions allow unauthorized access to restricted data through the API, resulting in high confidentiality impact.
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= 2211= 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP Commerce installation versionLocate and inspect the SAP Commerce version information in your deployment. This is typically visible in the admin console, installation manifest, or version metadata file included with your installation. Confirm whether the version matches 2211 (Commerce Cloud) or 2105/2205 (Hybris Commerce).Affected if The installed version equals exactly 2211 for Commerce Cloud, or equals exactly 2105 or 2205 for Hybris Commerce.
-
Verify OCC API endpoints are exposedReview your SAP Commerce endpoint configuration to determine whether Omni Commerce Connect (OCC) API endpoints are enabled and accessible. Check the OCC layer configuration files and web endpoint mappings.Affected if OCC API endpoints are enabled and publicly or internally accessible.
-
Inspect REST API endpoint access controlsExamine the authorization configuration for your OCC API endpoints. Look for the specific REST services that handle restricted or sensitive data. Verify whether proper authorization enforcement is configured on these endpoints.Affected if Authorization checks are missing, misconfigured, or can be bypassed for restricted data endpoints.
-
Test for unauthorized data accessUsing an authorized but low-privilege user account (or unauthenticated request if permitted), attempt to access known restricted data endpoints through the OCC API. Compare the returned data against what should be accessible based on the user role.Affected if Restricted or sensitive data is returned to a user who should not have access to that information.
You are affected if your SAP Commerce version is exactly 2211 (Cloud) or 2105/2205 (Hybris), OCC API endpoints are exposed, and restricted data can be accessed without proper authorization.
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.
From vendor dataApply SAP security patches for this vulnerability and review endpoint access controls to ensure proper authorization enforcement on restricted API endpoints.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37486 — 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-2023-37486 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