dbcve.org
Business OneApplication · Sap

CVE-2023-31403

HIGH · 8.0 CVSS v3.1 Published 2023-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
SAP Business One installation - version 10.0, does not perform proper authentication and authorization checks for SMB shared folder. As a result, any malicious user can read and write to the SMB shared folder. Additionally, the files in the folder can be executed or be used by the installation process leading to considerable impact on confidentiality, integrity and availability.

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 Business One version 10.0 lacks proper authentication and authorization checks for SMB shared folders used during installation. This allows any user to read/write to the SMB shared folder, and enables malicious files to be executed or used by the installation process, impacting confidentiality, integrity, and availability.

MitigationApply the vendor patch from SAP when available. In the interim, secure the SMB shared folder through network segmentation, proper authentication requirements (e.g., SMB signing, restricted share access), and strict access control lists to limit exposure.

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
Business OneApplication
Affected:= 10.0

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SAP Business One version
    Open SAP Business One client or check installation directory for version information. Common locations: C:\Program Files\SAP\SAP Business One\ or check Help > About in the client.
    Affected if Version is exactly 10.0 (build 10.0.x)
  2. Identify SMB shared folders used during installation
    Check installation logs or documentation for SMB share paths. Look for network paths (\\server\share) referenced in SAP Business One installation configuration files in the installation directory.
    Affected if Installation uses or previously used SMB network shares for distributing installation files or components
  3. Check SMB share permissions
    Right-click the SMB share in Windows Explorer > Properties > Sharing tab > Permissions. Also check NTFS permissions via Security tab. Run: net share [sharename] to list share details.
    Affected if Users other than intended administrators or installation service accounts have Read/Write permissions to the SMB share
  4. Verify SMB signing configuration
    Run Group Policy Result (gpresult /r) or check local security policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Microsoft network client: Digitally sign communications (if server). Also check registry: HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\RequireSecuritySignature
    Affected if SMB signing is disabled or not required on the network segment hosting the share
  5. Check for unauthorized files in SMB share
    Browse the SMB share contents via File Explorer or run: dir \\server\sharename /s. Inspect for unexpected .exe, .dll, .bat, .msi, or other executable files that were not part of the original installation.
    Affected if Unexpected executable or script files exist in the share that were not placed there by the installation team

A user is affected if SAP Business One version 10.0 is installed and SMB shared folders used during installation grant excessive permissions to unauthorized users.

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

Apply the vendor patch from SAP when available. In the interim, secure the SMB shared folder through network segmentation, proper authentication requirements (e.g., SMB signing, restricted share access), and strict access control lists to limit exposure.

Fix this in Business One Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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