{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-43002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-43002 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-43002 is a medium-severity missing authorization vulnerability in SAP_SE SAP S4/HANA (OData meta-data property), published on 13 May 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-43002 and fix it if it is affected.\n\nWhat it is: CVE-2025-43002 is a medium-severity missing authorization vulnerability in SAP_SE SAP S4/HANA (OData meta-data property), published on 13 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-43002 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP S4/HANA (OData meta-data property). 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-2025-43002/ (Markdown: https://insights.sbomify.com/CVE-2025-43002/index.md)","id":"CVE-2025-43002","markdown":"https://insights.sbomify.com/CVE-2025-43002/index.md","name":"CVE-2025-43002","record":{"aliases":["GHSA-v2rg-3wmw-65x9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP S4/HANA","requires_auth":"low_privilege","summary":"An authenticated attacker can access restricted information in SAP S4/HANA due to a missing authorization check in the OData meta-data property.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-472","name":"External Control of Assumed-Immutable Web Parameter"}],"description":"SAP S4CORE OData meta-data property allows an authenticated attacker to access restricted information due to missing authorization check. This could cause a low impact on confidentiality but integrity and availability of the application 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":"Missing Authorization check in SAP S4/HANA (OData meta-data property)","id":"CVE-2025-43002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Information Disclosure vulnerability in SAP S/4HANA (Private Cloud \u0026 On-Premise)","id":"CVE-2025-43003"},"packages":[],"prev":{"headline":"Multiple Privilege Escalation Vulnerabilities in SAPCAR","id":"CVE-2025-43001"},"products":["SAP S4/HANA (OData meta-data property)"],"published":"2025-05-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-13","vendors":["SAP_SE"]},"summary":"An authenticated attacker can access restricted information in SAP S4/HANA due to a missing authorization check in the OData meta-data property.","url":"https://insights.sbomify.com/CVE-2025-43002/"}