{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-35870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-35870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-35870 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Journal Entry Template), published on 11 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-35870 and fix it if it is affected.\n\nWhat it is: CVE-2023-35870 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Journal Entry Template), published on 11 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-35870 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP S/4HANA (Manage Journal Entry Template). 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-2023-35870/ (Markdown: https://insights.sbomify.com/CVE-2023-35870/index.md)","id":"CVE-2023-35870","markdown":"https://insights.sbomify.com/CVE-2023-35870/index.md","name":"CVE-2023-35870","record":{"aliases":["GHSA-jhwx-fm67-385p"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP S/4HANA ERP","requires_auth":"low_privilege","summary":"An attacker can intercept save requests to modify or delete journal entry templates, compromising data integrity and availability in SAP S/4HANA.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"s4core","vendor":"sap"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"When creating a journal entry template in SAP S/4HANA (Manage Journal Entry Template) - versions S4CORE 104, 105, 106, 107, an attacker could intercept the save request and change the template, leading to an impact on confidentiality and integrity of the resource. Furthermore, a standard template could be deleted, hence making the resource temporarily unavailable.","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":"Improper Access Control in SAP S/4HANA (Manage Journal Entry Template)","id":"CVE-2023-35870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory Corruption vulnerability in SAP Web Dispatcher","id":"CVE-2023-35871"},"packages":[],"prev":{"headline":"Denial of service in BIS Video Engine","id":"CVE-2023-35867"},"products":["SAP S/4HANA (Manage Journal Entry Template)"],"published":"2023-07-11","related":[{"cvss_score":7.7,"headline":"[CVE-2024-39592] Missing Authorization check in SAP PDCE","id":"CVE-2024-39592","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":5.4,"headline":"[CVE-2024-37172] Missing Authorization check in SAP S/4HANA Finance (Advanced Payment Management)","id":"CVE-2024-37172","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":5.4,"headline":"Missing Authorization check in SAP Manage Purchase Contracts App","id":"CVE-2023-40625","kev_date_added":null,"published":"2023-09-12"},{"cvss_score":4.3,"headline":"Missing Authorization check in SAP Fiori App (Manage Service Entry Sheets - Lean Services)","id":"CVE-2026-23688","kev_date_added":null,"published":"2026-02-10"},{"cvss_score":2.8,"headline":"Missing Authorization Check in Vendor Master Hierarchy","id":"CVE-2023-32112","kev_date_added":null,"published":"2023-05-09"}],"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-29","vendors":["SAP_SE"]},"summary":"An attacker can intercept save requests to modify or delete journal entry templates, compromising data integrity and availability in SAP S/4HANA.","url":"https://insights.sbomify.com/CVE-2023-35870/"}