Cyber Resilience

CVE-2024-45282

Sap S\/4 Hana 102 … 107

Published
08 October 2024
Modified
14 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0030 23th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2024-45282 is a medium-severity Trusting HTTP Permission Methods on the Server Side (CWE-650) vulnerability in Sap S\/4 Hana. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Fields which are in 'read only' state in Bank Statement Draft in Manage Bank Statements application, could be modified by MERGE method. The property of an OData entity representing assumably immutable method is not protected against external modifications leading to…

more

integrity violations. Confidentiality and Availability are not impacted.

CWE(s)
CWE-650

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-41368Same product: Sap S\/4 Hana
CVE-2023-41369Same product: Sap S\/4 Hana
CVE-2024-34691Same product: Sap S\/4 Hana
CVE-2026-0498Same product: Sap S\/4 Hana
CVE-2023-50422Same vendor: Sap
CVE-2025-0063Same vendor: Sap
CVE-2023-0016Same vendor: Sap
CVE-2021-33690Same vendor: Sap
CVE-2016-2386Same vendor: Sap
CVE-2021-38163Same vendor: Sap

Affected Assets

sap
s\/4 hana
102, 103, 104, 105, 106

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.1
  • V3.5.3
  • V4.1.4

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

AC-3 enforces authorizations for resource access without permitting unsafe assumptions about request methods to bypass checks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent flawed assumptions about HTTP method safety during design and coding.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover this server-side logic flaw through testing or scanning.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect and prevent vulnerabilities where GET requests cause unintended state changes.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper HTTP method usage and state-changing operation restrictions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include proper HTTP method handling and RESTful design to prevent state changes via GET.

A.8.28 Secure coding partial match
prevents

Secure coding practices directly address improper HTTP method usage and ensure state-changing operations use POST/PUT/DELETE.

References