CVE-2025-42995VulnerabilityPublished 10 Jun 2025

CVE-2025-42995: SAP MDM Server · Free of Memory not on the Heap

Affects SAP MDM ServerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately identify and inventory all SAP MDM Server instances running version 710.750 to assess exposure. 2) Implement network-level protections such as firewall rules and intrusion prevention systems (IPS) to restrict access to the SAP MDM Server's network ports, limiting exposure to trusted internal networks and known management hosts only. 3) Monitor network traffic for anomalous or malformed packets targeting the SAP MDM Server, using deep packet inspection tools to detect potential exploitation attempts. 4) Establish robust incident response procedures to quickly restart or failover SAP MDM Server instances in case of crashes to minimize downtime. 5) Engage with SAP support channels to obtain patches or hotfixes as soon as they become available, and plan for timely deployment. 6) Consider deploying SAP MDM Server instances in high-availability configurations or with load balancing to reduce the impact of single-instance failures. 7) Conduct regular security assessments and penetration testing focused on SAP infrastructure to identify and remediate similar memory management vulnerabilities proactively. These steps go beyond generic advice by focusing on network controls, monitoring, and operational resilience tailored to the specific vulnerability and product.

Description

SAP MDM Server Read function allows an attacker to send specially crafted packets which could trigger a memory read access violation in the server process that would then fail and exit unexpectedly causing high impact on availability with no impact on confidentiality and integrity of the application.

Impact

For European organizations using SAP MDM Server 710.750, this vulnerability poses a significant risk to operational continuity. The denial of service caused by the server crash can disrupt critical master data management processes, which are essential for maintaining accurate and consistent data across enterprise systems. This disruption can affect supply chain management, financial reporting, and customer data integrity indirectly by halting data synchronization and processing. Given SAP's widespread adoption in Europe, especially among large enterprises and manufacturing sectors, the availability impact could lead to operational downtime, financial losses, and reputational damage. However, since confidentiality and integrity are not compromised, the risk of data breaches or manipulation is minimal. The ease of exploitation without authentication or user interaction increases the threat level, as attackers can remotely trigger the crash without needing insider access or user involvement. Organizations with high dependency on SAP MDM for real-time data operations are particularly vulnerable to service interruptions.

CWE-590Free of Memory not on the Heap (opens in a new tab)
Variant weakness
The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().
Implementation
Only free pointers that you have called malloc on previously. This is the recommended solution. Keep track of which pointers point at the beginning of valid chunks and free them only once.
Implementation
Before freeing a pointer, the programmer should make sure that the pointer was previously allocated on the heap and that the memory belongs to the programmer. Freeing an unallocated pointer will cause undefined behavior in the program.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 11 Jul 2025, 00:32 UTC

WeaknessesCWE-590

Technical details

References

Community reviews

Related threats