Sploit.io - Search

Product: S/4 HANA (Map Treasury Correspondence Format Data), version: 104

CVE-2023-24524

Severity: MEDIUM

Description: SAP S/4 HANA Map Treasury Correspondence Format Data does not perform necessary authorization check for an authenticated user, resulting in escalation of privileges. This could allow an attacker to delete the data with a high impact to availability.

CVSS Score: 6.5

Priority

B

CISA Data

EPSS Data

  • EPSS: 0.003110000
  • Percentile: 0.543000000
  • Date: 2026-04-22

ExploitDB

No data available.

HackerOne Data

  • Rank: 9144
  • Reports submitted count: 0
  • Unknown: 0
  • None: 0
  • Low: 0
  • Medium: 0
  • High: 0
  • Critical: 0

GitHub PoCs

    Nuclei Templates

    No data available.

    VulnCheck Data

    Affected Products:

    • SAP S/4 HANA (Map Treasury Correspondence Format Data) - Versions: 104, 105

    References:

    Risk Assessment

    1. Risk Assessment
    The vulnerability CVE-2023-24524 affects SAP S/4 HANA specifically within the Map Treasury Correspondence Format Data module. It stems from a missing authorization check, meaning an authenticated user, with low privileges, can escalate their privileges and delete data. The base CVSS score is 6.5 (Medium), indicating a moderate risk. The high availability impact is the most significant concern. While confidentiality and integrity aren’t directly impacted, the ability to delete data can disrupt business processes dependent on the Treasury Correspondence Format Data. The likelihood of exploitation is moderate, given the need for an authenticated user already possessing some level of access to the system. However, the ease of exploitation, once authenticated, is low because the attacker simply needs to delete the data. The business impact could range from minor disruptions in report generation to significant delays in treasury operations, depending on how critical the affected data is to core business functions. The EPSS score of 0.003110000 suggests a relatively low but not insignificant probability of exploitation in the wild.

    2. Potential Attack Scenarios
    An attacker, already authenticated as a low-privileged user within the SAP S/4 HANA system, could exploit this vulnerability to disrupt treasury correspondence processes. The attack vector is network-based, meaning the attacker can initiate the attack remotely. The attack process involves the authenticated user leveraging their existing credentials to delete critical Treasury Correspondence Format Data. This could be accomplished through standard SAP transaction codes or API calls. The potential outcome is the loss of Treasury Correspondence data, potentially impacting reporting, reconciliation, and communication with financial institutions. For example, a user responsible for generating monthly treasury reports might delete the data used to create those reports, causing a delay in reporting and potentially impacting financial decision-making. The impact is primarily on availability, making the data unavailable for its intended purpose.

    3. Mitigation Recommendations
    The primary mitigation for CVE-2023-24524 is to apply the latest SAP security patch. SAP recommends implementing the corrections outlined in SAP Security Note 2985905. This patch specifically addresses the missing authorization check within the Map Treasury Correspondence Format Data module. In addition, organizations should review user permissions and ensure the principle of least privilege is applied. Specifically, assess which users have the ability to delete data within the affected module and confirm whether that level of access is necessary for their roles. Regularly audit user activity to detect any unusual deletion patterns. Finally, monitor the PacketStorm Security website (https://packetstormsecurity.com/search/?q=CVE-2023-24524) for any newly discovered exploits and adapt mitigation strategies accordingly.

    4. Executive Summary
    SAP S/4 HANA contains a vulnerability (CVE-2023-24524) that allows authenticated users to escalate privileges and delete data within the Map Treasury Correspondence Format Data module. While not a critical vulnerability, the potential for disruption to treasury operations is significant. An attacker, already logged into the system, can delete important data, impacting reporting and communication with financial institutions. To address this risk, we recommend applying the latest SAP security patch (Security Note 2985905) as soon as possible. Additionally, review user permissions to ensure users only have the necessary access to perform their duties. Prompt action is recommended to minimize the potential impact on our treasury processes and ensure data availability. This vulnerability represents a moderate risk that, if exploited, could lead to delays in financial reporting and potentially impact key financial decisions.