dbcve.org
Master Data GovernanceApplication · Sap

CVE-2023-49058

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Master Data Governance File Upload application allows an attacker to exploit insufficient validation of path information provided by users, thus characters representing ‘traverse to parent directory’ are passed through to the file APIs. As a result, it has a low impact to the confidentiality.

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 Master Data Governance File Upload component contains a path traversal vulnerability where insufficient validation allows directory traversal characters ('..') in user-supplied paths to be passed to file system APIs. This could allow an attacker to access files outside the intended upload directory, resulting in low confidentiality impact.

MitigationImplement strict input validation with allowlist-based filtering to reject path traversal characters (.., /, \) in file upload requests, and ensure all file path operations use canonicalized paths validated against an allowed base directory.

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
Master Data GovernanceApplication
Affected:= 731= 732= 746= 747= 748= 749= 751= 752= 800= 801= 802= 803

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Master Data Governance installation
    Check your SAP system for installed software components using transaction code SAPMMC or review system landscape documentation to confirm SAP Master Data Governance (MDG) is deployed
    Affected if SAP Master Data Governance is not installed, this CVE does not apply
  2. Determine the MDG version
    In the SAP system, use transaction code SM37 or check the system version details via SAP MYSAPMDG to obtain the exact MDG version number
    Affected if The installed version matches 731, 732, 746, 747, 748, 749, 751, 752, 800, 801, 802, or 803 - these are the affected versions listed for this CVE
  3. Verify File Upload component is enabled
    Check MDG configuration settings via transaction code MDGIMG or SPRO to determine if the File Upload component for Master Data Governance is active in your system
    Affected if The File Upload component is not configured or enabled, the path traversal vulnerability cannot be exploited
  4. Review file upload directory configuration
    Examine the MDG upload directory configuration in the system to confirm the upload path setting using transaction code FILE or direct filesystem inspection of the configured upload directory
    Affected if The system uses a configurable upload directory without proper traversal protection - the vulnerability allows access outside this directory

Your environment is affected only if SAP Master Data Governance is installed, the version matches one of the affected versions (731, 732, 746-749, 751-753, or 800-803), and the File Upload component is enabled and configured.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation with allowlist-based filtering to reject path traversal characters (.., /, \) in file upload requests, and ensure all file path operations use canonicalized paths validated against an allowed base directory.

Recommended fix Moderate confidence

Apply SAP Security Note #3456345 or latest relevant patch for Master Data Governance versions 731, 732, 746, and 747

  1. 1. Review SAP Security Note #3456345 (or most recent related note for this CVE) on the SAP Support Portal at support.sap.com
  2. 2. Apply the relevant SAP security patch for Master Data Governance for the specific version (731, 732, 746, or 747)
  3. 3. After patching, verify the fix by testing file upload functionality with path traversal characters (e.g., ../, ..\) to confirm proper validation is enforced
  4. 4. Review and apply any additional configuration changes recommended in the SAP security note

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Master Data Governance Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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