dbcve.org
Business OneApplication · Sap

CVE-2026-24319

MEDIUM · 5.8 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated

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
In SAP Business One, sensitive information is written to the application�s memory dump files without obfuscation. Gaining access to this information could potentially lead to unauthorized operations within the B1 environment, including modification of company data. This issue results in a high impact on confidentiality and integrity, with no impact on 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 writes sensitive information to application memory dump files in plaintext/unobfuscated form. When these dump files are generated (during crashes, debugging, or diagnostics), any sensitive data present in memory at that time gets captured without redaction. An attacker with access to these dump files can extract credentials, business data, or other sensitive information that could enable unauthorized operations and data modification within the B1 environment.

MitigationThe primary remediation involves implementing data obfuscation or exclusion logic before writing any data to memory dump files. This may include sanitizing sensitive fields, encrypting dump contents, or preventing sensitive data from being included in dumps altogether. Additionally, securing dump file storage locations and access controls can reduce exposure risk.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:R/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 Business One version 10.0 is installed
    Check the installed version of SAP Business One in the system via the SAP Business One client, version information in the installer, or system information tool. Compare your installed version against the affected range (version 10.0).
    Affected if The installed version is exactly 10.0
  2. Locate memory dump file generation settings
    Inspect SAP Business One configuration files, diagnostic settings, or logging configurations that control whether memory dumps are enabled or generated. Look for settings related to crash dumps, debugging traces, or diagnostic file output.
    Affected if Memory dump or diagnostic file generation is enabled in the SAP Business One configuration
  3. Search for existing memory dump files
    Search the SAP Business One installation directory and associated data directories for file types commonly associated with memory dumps (such as .dmp, .mdmp, .hdmp, crash reports, or diagnostic output files).
    Affected if Any memory dump, crash dump, or diagnostic files exist in the SAP Business One environment
  4. Inspect dump files for sensitive data
    If dump files exist, examine their contents (using a text editor or string search utility) for plaintext sensitive information such as credentials, user passwords, business data, or other confidential fields that should have been obfuscated or excluded.
    Affected if Dump files contain plaintext credentials, passwords, or other sensitive business data in unobfuscated form
  5. Review dump file access controls
    Check file system permissions on directories where dump files are stored to determine if unauthorized users or processes could access these files.
    Affected if Dump files or their storage directories have overly permissive access controls allowing unauthorized access

A user is affected if they have SAP Business One version 10.0 with memory dump generation enabled and dump files exist that contain plaintext sensitive information accessible to unauthorized parties.

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

The primary remediation involves implementing data obfuscation or exclusion logic before writing any data to memory dump files. This may include sanitizing sensitive fields, encrypting dump contents, or preventing sensitive data from being included in dumps altogether. Additionally, securing dump file storage locations and access controls can reduce exposure risk.

Fix this in Business One Scoped from the published advisory
  • Consultation8.0 h
  • Implementation60.0 h
  • Testing24.0 h
  • Review / QA12.0 h
104.0 hours of engineering $18,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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