dbcve.org
Enterprise Extension Financial ServicesPlugin / extension · Sap

CVE-2019-0384

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 functionalities that require user identity.

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 confidence

SAP Treasury and Risk Management's transaction management component lacks proper authorization checks for functionalities requiring user identity verification. This allows authenticated users to potentially execute unauthorized transactions or access transaction management functions outside their intended permissions scope.

MitigationApply the SAP security patches for S4CORE (versions 1.01-1.04) and EA-FINSERV (versions 6.0-8.0) as specified in the SAP Security Note. Verify authorization controls are enforced post-patch.

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. Identify installed SAP Treasury and Risk Management component
    In SAP, go to system information or use transaction code SM37 to check running jobs, or use transaction code SPAM to check installed software components. Look for components named 'EA-FINSERV' or 'S4CORE' in the installed software inventory.
    Affected if The component EA-FINSERV or S4CORE is installed on the system
  2. Verify the installed version of SAP Enterprise Extension Financial Services (EA-FINSERV)
    Use SAP transaction code SPAM (Support Package Manager) or SAINT (Add-On Installation Tool) to view installed support packages. Locate EA-FINSERV component and note its version number.
    Affected if The installed version is 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, or 8.0
  3. Verify the installed version of SAP Treasury and Risk Management S4CORE
    Use SAP transaction code SPAM or SAINT to view installed software components. Look for 'S4CORE' component and note its version number.
    Affected if The installed version is 1.01, 1.02, 1.03, or 1.04
  4. Check if transaction management functionality is accessible to users
    Log into the SAP system with a standard user account and attempt to access transaction management functions in Treasury and Risk Management module. Use transaction codes such as 'FTR_MANAGE' or navigation paths within Treasury and Risk Management.
    Affected if A user can access transaction management functions without proper authorization enforcement
  5. Review user authorization profiles for transaction management
    Use transaction code PFCG to examine authorization roles assigned to users. Check if roles related to Treasury and Risk Management transaction management have unrestricted access or are missing proper authorization objects.
    Affected if Users have roles with elevated privileges that allow execution of transactions outside their intended permissions scope

The environment is affected if SAP Treasury and Risk Management components (EA-FINSERV versions 6.0-8.0 or S4CORE versions 1.01-1.04) are installed and the transaction management functionality lacks proper authorization controls.

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 SAP security patches for S4CORE (versions 1.01-1.04) and EA-FINSERV (versions 6.0-8.0) as specified in the SAP Security Note. Verify authorization controls are enforced post-patch.

Fix this in Enterprise Extension Financial Services Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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