CVE-2019-0370
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 · uneditedDue to missing input validation, SAP Financial Consolidation, before versions 10.0 and 10.1, enables an attacker to use crafted input to interfere with the structure of the surrounding query leading to XPath Injection.
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 confidenceThis is an XPath Injection vulnerability in SAP Financial Consolidation caused by missing input validation on user-supplied data. An attacker can use crafted input to manipulate the XPath query structure, potentially extracting unauthorized data from XML-based data stores or bypassing authentication.
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= 10.0= 10.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP Financial Consolidation installationLocate the SAP Financial Consolidation installation directory and check for the application executable or service. Common paths include C:\Program Files\SAP\FC or similar. Use system inventory tools to list installed SAP software.Affected if SAP Financial Consolidation is installed on the system
-
Determine installed versionCheck the exact version of SAP Financial Consolidation. This is typically available in the application itself (Help > About), in the installation logs, or via SAP-specific version detection tools. Look for version strings '10.0' or '10.1'.Affected if The installed version is exactly 10.0 or exactly 10.1
-
Check for XPath query functionalityIdentify if the SAP Financial Consolidation instance uses XML data stores or XPath-based queries. This may be evident in configuration files, custom reports, or data import/export features that process XML content.Affected if The application uses XML-based data storage or XPath queries in any feature
-
Identify exposed user input fieldsReview web interfaces or client applications of SAP Financial Consolidation for input fields that accept user data. Focus on search fields, filter options, report parameters, or data entry forms that could interact with XML data.Affected if User-accessible input fields exist that could be used to inject XPath syntax
-
Audit XPath query implementationExamine application logs, XML configuration files, or custom scripts to determine whether user-supplied input is concatenated directly into XPath expressions without proper sanitization or parameterized query handling.Affected if User input is used in XPath queries without input validation or prepared statements
The environment is affected if SAP Financial Consolidation version 10.0 or 10.1 is installed AND the application exposes any user input fields that interact with XML data through XPath queries.
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 dataUpgrade SAP Financial Consolidation to version 10.0 or 10.1. Additionally, implement proper input validation and use parameterized/prepared XPath queries to prevent injection.
- 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-0370 — 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-0370 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