CVE-2023-37487
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 · uneditedSAP Business One (Service Layer) - version 10.0, allows an authenticated attacker with deep knowledge perform certain operation to access unintended data over the network which could lead to 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 Business One Service Layer in version 10.0 contains an information disclosure vulnerability where an authenticated attacker with deep knowledge can perform certain operations to access data they are not authorized to view over the network. This results in high confidentiality impact but no impact on integrity or availability.
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= 10.0CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Verify SAP Business One versionCheck the installed SAP Business One version via the SAP Business One Administration Tools, System Landscape Directory, or by querying the Service Layer version endpoint (typically /b1s/v1/ version info). Compare against the affected version 10.0.Affected if The installed version is exactly 10.0 and Service Layer is exposed.
-
Confirm Service Layer is enabledVerify that the SAP Business One Service Layer is installed and running. Check if the Service Layer application (usually hosted on port 50000 by default) is accessible and responding to HTTP requests.Affected if Service Layer is installed and accessible over the network.
-
Identify exposed Service Layer endpointsEnumerate Service Layer OData endpoints accessible over the network. Review which service endpoints (such as /b1s/v1/) are exposed and their associated business objects.Affected if Service Layer endpoints are network-accessible without proper network segmentation.
-
Review authorization configurationInspect the authorization configuration for Service Layer endpoints. Check user permissions mapping and data access controls within the SAP Business One Service Layer authorization framework.Affected if Users can invoke Service Layer operations beyond their assigned permission scope.
A user is affected if they run SAP Business One version 10.0 with Service Layer enabled and accessible, and the authorization controls on Service Layer endpoints do not properly restrict data access to authorized users.
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 dataReview and enforce proper authorization controls on Service Layer endpoints to ensure users can only access data they are explicitly permitted to access. Apply any available SAP security patches for this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37487 — 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-37487 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