{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45282 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45282 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45282 is a medium-severity vulnerability in SAP_SE SAP S/4 HANA (Manage Bank Statements), published on 8 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45282 and fix it if it is affected.\n\nWhat it is: CVE-2024-45282 is a medium-severity vulnerability in SAP_SE SAP S/4 HANA (Manage Bank Statements), published on 8 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45282 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP S/4 HANA (Manage Bank Statements). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-45282/ (Markdown: https://insights.sbomify.com/CVE-2024-45282/index.md)","id":"CVE-2024-45282","markdown":"https://insights.sbomify.com/CVE-2024-45282/index.md","name":"CVE-2024-45282","record":{"aliases":["GHSA-3wwx-rqjr-vjcc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP S/4 HANA","requires_auth":"low_privilege","summary":"Attackers can modify read-only bank statement fields via HTTP verb tampering, compromising data integrity in SAP S/4 HANA.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"s\\/4_hana","vendor":"sap"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-650","name":"Trusting HTTP Permission Methods on the Server Side"}],"description":"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 integrity violations. Confidentiality and Availability are not impacted.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HTTP Verb Tampering in SAP S/4 HANA(Manage Bank Statements)","id":"CVE-2024-45282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure vulnerability in SAP NetWeaver AS for Java (Destination Service)","id":"CVE-2024-45283"},"packages":[],"prev":{"headline":"DLL hijacking vulnerability in SAP BusinessObjects Business Intelligence Platform","id":"CVE-2024-45281"},"products":["SAP S/4 HANA (Manage Bank Statements)"],"published":"2024-10-08","related":[{"cvss_score":9.1,"headline":"Code Injection vulnerability in SAP S/4HANA (Private Cloud and On-Premise)","id":"CVE-2026-0498","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":6.5,"headline":"Missing Authorization check in SAP S/4HANA (Manage Incoming Payment Files)","id":"CVE-2024-34691","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":3.5,"headline":"External Entity Loop vulnerability in SAP S/4HANA (Create Single Payment application)","id":"CVE-2023-41369","kev_date_added":null,"published":"2023-09-12"},{"cvss_score":2.7,"headline":"Insecure Direct Object Reference (IDOR) vulnerability in S4 HANA (Manage checkbook apps)","id":"CVE-2023-41368","kev_date_added":null,"published":"2023-09-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-09","vendors":["SAP_SE"]},"summary":"Attackers can modify read-only bank statement fields via HTTP verb tampering, compromising data integrity in SAP S/4 HANA.","url":"https://insights.sbomify.com/CVE-2024-45282/"}