dbcve.org
Supplier Relationship Management Mdm CatalogApplication · Sap

CVE-2018-2449

HIGH · 8.6 CVSS v3.0 Published 2018-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 SRM MDM Catalog versions 3.73, 7.31, 7.32 in (SAP NetWeaver 7.3) - import functionality does not perform authentication checks for valid repository user. This is an unauthenticated functionality that you can use on windows machines to do SMB relaying.

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 confidence

SAP SRM MDM Catalog import functionality lacks authentication validation, allowing unauthenticated attackers to access the import mechanism. On Windows systems, this can be exploited for SMB relaying attacks since the vulnerable component handles SMB connections without verifying the requesting user's credentials.

MitigationApply appropriate SAP security patches/notes for CVE-2018-2449. If patches are unavailable, implement network segmentation to restrict SMB access and disable the import functionality until a fix is available.

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
Supplier Relationship Management Mdm CatalogApplication
Affected:= 3.73= 7.31= 7.32

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
Low
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP SRM MDM Catalog installation
    Check if SAP Supplier Relationship Management MDM Catalog component is installed on the system by reviewing installed SAP software packages or checking for MDM Catalog executables/services in the SAP system directory (typically under /usr/sap or the SAP installation root)
    Affected if The SAP SRM MDM Catalog component is present on the system
  2. Verify installed version
    Locate the MDM Catalog version information in the SAP system: check the SAP System Landscape Directory (SLD), transaction code SPAM for SAP SRM component versions, or examine the MDM Catalog binary/executable version properties
    Affected if The installed version matches 3.73, 7.31, or 7.32 exactly (exact version match required)
  3. Confirm MDM Catalog import functionality is enabled
    Check if the MDM Catalog import service is running and accessible. This typically involves verifying the MDM Catalog HTTP/HTTPS endpoint is exposed and the import module is loaded in the SAP system configuration (check via transaction SM37 for MDM-related jobs or RFC destinations)
    Affected if The import functionality is active and the service is listening for import requests
  4. Check Windows platform for SMB exposure
    Determine the operating system hosting the SAP application. On Windows systems, verify if SMB ports (445/tcp, 139/tcp) are open and accessible from the network, as the vulnerability allows SMB relaying attacks on Windows hosts
    Affected if The SAP system runs on Windows and has exposed SMB ports (445 or 139)
  5. Assess network accessibility of import service
    Review network configuration to determine if the MDM Catalog import endpoint is reachable from untrusted networks. Check firewall rules and SAP ICM/Internet Communication Manager configuration for exposed ports related to MDM functionality
    Affected if The import functionality is exposed to network segments beyond trusted internal networks

The environment is affected if SAP SRM MDM Catalog versions 3.73, 7.31, or 7.32 are installed with the import functionality enabled and accessible, particularly on Windows systems with exposed SMB ports.

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 appropriate SAP security patches/notes for CVE-2018-2449. If patches are unavailable, implement network segmentation to restrict SMB access and disable the import functionality until a fix is available.

Fix this in Supplier Relationship Management Mdm Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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