CVE-2019-0361
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 Supplier Relationship Management (Master Data Management Catalog - SRM_MDM_CAT, before versions 3.73, 7.31, 7.32) does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability.
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 Supplier Relationship Management (SRM_MDM_CAT) contains a Cross-Site Scripting (XSS) vulnerability due to insufficient encoding of user-controlled inputs. An attacker could inject malicious scripts through unsanitized input fields in the Master Data Management Catalog component, potentially compromising user sessions or performing actions on behalf of authenticated users.
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= 3.73= 7.31= 7.32CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 SRM installation and versionQuery the SAP system for installed software components using transaction code SM37 or check the SAP System Landscape Directory (SLD). Look for component SRM_MDM (Supplier Relationship Management - Master Data Management) and note the version number.Affected if The installed version of SRM_MDM falls within or before the affected version ranges (3.73, 7.31, 7.32).
-
Verify SRM_MDM_CAT component is deployedIn the SAP system, use transaction code SE11 or SPAM to check if the SRM_MDM_CAT (Master Data Management Catalog) component is installed and active in the system.Affected if The SRM_MDM_CAT component is present and deployed in the SAP environment.
-
Check MDM Catalog configuration and accessibilityAccess the Master Data Management Catalog configuration via transaction code MDG_CONFIG or verify web service endpoint /sap/bc/rest/mdm_cat is exposed. Check if the catalog is publicly or internally accessible.Affected if The MDM Catalog component is accessible without proper authentication controls or input validation settings.
-
Inspect input fields for encoding settingsReview SAP MDM Catalog transaction logs or use transaction code SE80 to examine the data flow in catalog input screens. Look for custom implementations that handle user-supplied data in catalog management screens.Affected if Custom implementations or configurations exist that allow unsanitized user input to be processed through the MDM Catalog component.
A system is affected if SAP SRM with SRM_MDM_CAT component is installed at a version that precedes the patched versions (3.73, 7.31, or 7.32) and the Master Data Management Catalog feature is accessible to users.
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 dataApply the SAP security patch for CVE-2019-0361 by upgrading to versions 3.73, 7.31, or 7.32 (depending on your release line) to resolve the input encoding deficiency.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0361 — 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-0361 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