{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-32112 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32112 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32112 is a low-severity missing authorization vulnerability in SAP_SE Vendor Master Hierarchy, published on 9 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-32112 and fix it if it is affected.\n\nWhat it is: CVE-2023-32112 is a low-severity missing authorization vulnerability in SAP_SE Vendor Master Hierarchy, published on 9 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-32112 in the wild and no public exploit code.\n\nAffected product: SAP_SE Vendor Master Hierarchy. 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-32112/ (Markdown: https://insights.sbomify.com/CVE-2023-32112/index.md)","id":"CVE-2023-32112","markdown":"https://insights.sbomify.com/CVE-2023-32112/index.md","name":"CVE-2023-32112","record":{"aliases":["GHSA-5vh6-vprx-fjvm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SAP Vendor Master Hierarchy","requires_auth":"low_privilege","summary":"An authenticated user can modify vendor master data due to missing authorization checks, compromising system integrity.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"s4core","vendor":"sap"},{"product":"vendor_master_hierarchy","vendor":"sap"}],"cvss":{"score":2.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Vendor Master Hierarchy - versions SAP_APPL 500, SAP_APPL 600, SAP_APPL 602, SAP_APPL 603, SAP_APPL 604, SAP_APPL 605, SAP_APPL 606, SAP_APPL 616, SAP_APPL 617, SAP_APPL 618, S4CORE 100, does not perform necessary authorization checks for an authenticated user to access some of its function. This could lead to modification of data impacting the integrity of the system.","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":"Missing Authorization Check in Vendor Master Hierarchy","id":"CVE-2023-32112","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":"Information Disclosure vulnerability in SAP GUI for Windows","id":"CVE-2023-32113"},"packages":[],"prev":{"headline":"Memory Corruption vulnerability in SAP PowerDesigner (Proxy)","id":"CVE-2023-32111"},"products":["Vendor Master Hierarchy"],"published":"2023-05-09","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":6.3,"headline":"Improper Access Control in SAP S/4HANA (Manage Journal Entry Template)","id":"CVE-2023-35870","kev_date_added":null,"published":"2023-07-11"},{"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"}],"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":"2025-01-28","vendors":["SAP_SE"]},"summary":"An authenticated user can modify vendor master data due to missing authorization checks, compromising system integrity.","url":"https://insights.sbomify.com/CVE-2023-32112/"}