dbcve.org
Enterprise Extension Financial ServicesPlugin / extension · Sap

CVE-2019-0383

HIGH · 8.8 CVSS v3.1 Published 2019-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Transaction Management in SAP Treasury and Risk Management (corrected in S4CORE versions 1.01, 1.02, 1.03, 1.04 and EA-FINSERV versions 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, 8.0) does not perform necessary authorization checks for an authenticated user, resulting in 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 · high confidence

The transaction management component in SAP Treasury and Risk Management fails to enforce proper authorization checks for authenticated users, allowing privilege escalation. An authenticated attacker with standard user privileges can exploit missing authorization validation in transaction processing to gain elevated access to sensitive treasury functions and data.

MitigationApply the corrected S4CORE versions (1.01, 1.02, 1.03, 1.04) and EA-FINSERV versions (6.0, 6.03-6.06, 6.16-6.18, 8.0) via SAP Security Notes. Review user role assignments and transaction authorizations in the affected SAP Treasury modules.

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
Enterprise Extension Financial ServicesPlugin / extension
Affected:= 6.0= 6.03= 6.04= 6.05= 6.06= 6.16= 6.17= 6.18= 8.0
Treasury And Risk Management \(s4core\)Application
Affected:= 1.01= 1.02= 1.03= 1.04

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

CVSS:3.1/AV:N/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 if SAP Treasury and Risk Management component is installed
    In SAP transaction SM37, check for running processes related to Treasury functions, or use SAP MII transaction to list installed software components and look for EA-FINSERV or Treasury modules in the component list
    Affected if The system has EA-FINSERV or S4CORE Treasury components installed
  2. Check EA-FINSERV component version
    Use SAP transaction SAPCM to view installed software components, navigate to Enterprise Extensions > Financial Services, and record the exact version number (6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, or 8.0)
    Affected if The installed version matches any of the affected versions: 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, or 8.0
  3. Check S4CORE Treasury component version
    Use SAP transaction SAPCM to view installed software components, navigate to S4CORE or Treasury and Risk Management section, and record the exact version number (1.01, 1.02, 1.03, or 1.04)
    Affected if The installed version matches any of the affected versions: 1.01, 1.02, 1.03, or 1.04
  4. Identify exposed transaction processing features
    Review SAP transaction codes related to Treasury transaction management such as FTR_TCR, FTR_PROCESS, or similar Treasury transaction processing transactions listed in the system
    Affected if Treasury transaction processing transactions are available and accessible to standard users

A user is affected if their SAP system has Treasury and Risk Management installed with EA-FINSERV versions 6.0 through 8.0 (excluding 6.01, 6.02, 6.07-6.15) or S4CORE versions 1.01-1.04, allowing standard users to access transaction processing functions.

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 corrected S4CORE versions (1.01, 1.02, 1.03, 1.04) and EA-FINSERV versions (6.0, 6.03-6.06, 6.16-6.18, 8.0) via SAP Security Notes. Review user role assignments and transaction authorizations in the affected SAP Treasury modules.

Fix this in Enterprise Extension Financial Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

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