CVE-2019-0280
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 · uneditedSAP Treasury and Risk Management (EA-FINSERV 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18 and 8.0; S4CORE 1.01, 1.02 and 1.03), does not perform necessary authorization checks for authorization objects T_DEAL_DP and T_DEAL_PD , 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 confidenceSAP Treasury and Risk Management fails to enforce authorization checks on authorization objects T_DEAL_DP and T_DEAL_PD, allowing authenticated users to perform operations outside their intended privilege level. This enables privilege escalation within the Treasury module.
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.03= 6.04= 6.05= 6.06= 6.16= 6.17= 6.18= 8.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed SAP Treasury versionUse SAP transaction code SMAN or system reports to determine the exact version of SAP Treasury and Risk Management installed in your systemAffected if The installed version matches any of these: 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, or 8.0
-
Verify authorization object T_DEAL_DP existenceUse transaction code SU03 or SU21 to search for and inspect authorization object T_DEAL_DP in the systemAffected if The authorization object T_DEAL_DP exists in the system without proper field checks or with incomplete authorization maintenance
-
Verify authorization object T_DEAL_PD existenceUse transaction code SU03 or SU21 to search for and inspect authorization object T_DEAL_PD in the systemAffected if The authorization object T_DEAL_PD exists in the system without proper field checks or with incomplete authorization maintenance
-
Review user roles containing affected objectsUse transaction code PFCG to search for roles that include T_DEAL_DP or T_DEAL_PD authorization objects and examine their defined valuesAffected if Roles grant overly broad access to these objects allowing operations beyond the intended privilege level
-
Check transaction execution without proper authorizationTest executing Treasury deal processing transactions (such as transaction codes related to deal portfolio management) using a low-privilege user account to see if operations succeed without proper authorizationAffected if Low-privilege users can perform deal processing or portfolio operations that should require higher-level authorization
You are affected if your SAP Treasury version is 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18, or 8.0 AND the authorization objects T_DEAL_DP or T_DEAL_PD are present without proper field-level authorization checks.
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 dataImplement proper authorization checks for T_DEAL_DP and T_DEAL_PD objects in the affected SAP modules. Review and adjust user role assignments to ensure least-privilege access to deal processing and deal portfolio functions.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0280 — 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-0280 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