dbcve.org
Portfolio And Project ManagementApplication · Sap

CVE-2019-0399

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
SAP Portfolio and Project Management, before versions S4CORE 102, 103, EPPM 100 and CPRXRPM 500_702, 600_740, 610_740; unintentionally allows a user to discover accounting information of the Projects in Project dashboard, leading to Information Disclosure.

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 Portfolio and Project Management contains an information disclosure vulnerability in the Project dashboard where users can discover accounting information for Projects that they should not have access to. This is an access control/authorization flaw in the dashboard component that allows unauthorized visibility into financial data.

MitigationApply the relevant SAP security patch for this vulnerability (refer to SAP Security Note 2818707) and review role-based access control (BRF+) configurations for the Project dashboard to ensure proper segregation of accounting information.

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
Portfolio And Project ManagementApplication
Affected:= cprxrpm_500_702= cprxrpm_600_740= cprxrpm_610_740= eppm_100= s4core_102= s4core_103

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify SAP Portfolio and Project Management version
    Execute SAP transaction code SPAM or use transaction code SM37 to check installed software component versions. Look for components: CPRXRPM, EPPM, or S4CORE in the system.
    Affected if Installed version matches any of: cprxrpm_500_702, cprxrpm_600_740, cprxrpm_610_740, eppm_100, s4core_102, s4core_103
  2. Confirm Project dashboard component is active
    Access the SAP Fiori launchpad or SAP GUI and navigate to the Project Dashboard component within Portfolio and Project Management. Check if the dashboard is accessible via transaction code /n/PPM/PROJ_DASHBOARD or similar PPM transactions.
    Affected if The Project dashboard component is accessible and in use in the system
  3. Verify BRF+ authorization configuration for dashboard
    Access SAP transaction code BRF+ (or /n/BRFplus) and examine the authorization settings for the Project dashboard financial data queries. Check role assignments for user access to accounting information blocks.
    Affected if BRF+ rules for the Project dashboard allow broad access or are not properly restricting financial data visibility to authorized roles only
  4. Test unauthorized access to project accounting data
    As a test user without project ownership or financial reviewer roles, attempt to access the Project dashboard and view accounting information for projects outside your assigned scope.
    Affected if A user without proper authorization can view accounting data for projects they are not assigned to

The environment is affected if SAP Portfolio and Project Management is installed at any of the listed versions AND the Project dashboard is active with potentially misconfigured BRF+ authorization settings.

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 relevant SAP security patch for this vulnerability (refer to SAP Security Note 2818707) and review role-based access control (BRF+) configurations for the Project dashboard to ensure proper segregation of accounting information.

Fix this in Portfolio And Project Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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