CVE-2019-0386
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 · uneditedOrder processing in SAP ERP Sales (corrected in SAP_APPL 6.0, 6.02, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18) and S4HANA Sales (corrected in S4CORE 1.0, 1.01, 1.02, 1.03, 1.04) does not execute the required authorization checks for an authenticated user, which can result in an escalation of privileges.
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 confidenceThis is an authorization bypass vulnerability in SAP ERP Sales and S4HANA Sales order processing. The system fails to perform required authorization checks for authenticated users during order operations, allowing privilege escalation where a user can perform actions beyond their assigned authorization level.
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= 6.0= 6.02= 6.03= 6.04= 6.05= 6.06= 6.16= 6.17= 6.18= 1.0= 1.01= 1.02= 1.03= 1.04CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 product typeUse transaction code SM51 or log into SAPgui to view system information. Look for whether the system is labeled as SAP ERP (ECC) or SAP S/4HANA.Affected if The system is running SAP ERP Sales or SAP S/4HANA Sales.
-
Determine SAP_APPL version (for ERP Sales)Execute transaction code SM37, then navigate to System > Status > Component Information. Locate the SAP_APPL component and note its version number.Affected if The SAP_APPL version is 6.0, 6.02, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, or 6.18.
-
Determine S4CORE version (for S/4HANA Sales)Execute transaction code SM37, then navigate to System > Status > Component Information. Locate the S4CORE component and note its version number.Affected if The S4CORE version is 1.0, 1.01, 1.02, 1.03, or 1.04.
-
Confirm Sales order processing is activeUse transaction code VA01 (Create Sales Order) or VA03 (Display Sales Order) to verify that the Sales module is accessible and operational in the environment.Affected if Sales order transactions VA01, VA02, or VA03 are accessible and functional.
-
Review authorization roles for order operationsExecute transaction code SUIM, then search for authorization objects related to Sales (such as V_VBAK_VKO or V_VBAK_AKT). Compare assigned roles against expected business roles to detect any unexpected privilege assignments.Affected if Users possess authorization objects for sales order operations beyond what their assigned business role should permit.
You are affected if your SAP system runs ERP Sales (SAP_APPL 6.0-6.18) or S/4HANA Sales (S4CORE 1.0-1.04) and sales order processing is active, particularly if authorization role assignments appear inconsistent with intended privilege levels.
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 the relevant SAP security patches (SAP notes) for affected SAP_APPL versions (6.0-6.18) and S4CORE versions (1.0-1.04), or upgrade to patched releases. Verify authorization roles and profiles after patching.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0386 — 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-2019-0386 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