{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-42475 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-42475 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42475 is a medium-severity vulnerability in SAP_SE SAP S/4HANA Core, published on 10 Oct 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-42475 and fix it if it is affected.\n\nWhat it is: CVE-2023-42475 is a medium-severity vulnerability in SAP_SE SAP S/4HANA Core, published on 10 Oct 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-42475 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP S/4HANA Core. 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-42475/ (Markdown: https://insights.sbomify.com/CVE-2023-42475/index.md)","id":"CVE-2023-42475","markdown":"https://insights.sbomify.com/CVE-2023-42475/index.md","name":"CVE-2023-42475","record":{"aliases":["GHSA-wj24-9p82-86v2"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP S/4HANA Core","requires_auth":"low_privilege","summary":"A low-privileged attacker can read server files due to a vulnerable file storage location in the Statutory Reporting application.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"s\\/4hana","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:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"The Statutory Reporting application has a vulnerable file storage location, potentially enabling low privileged attacker to read server files with minimal impact on confidentiality.","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":"Information Disclosure Vulnerability in Statutory Reporting","id":"CVE-2023-42475","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Cross Site Scripting vulnerability in SAP BusinessObjects Web Intelligence","id":"CVE-2023-42476"},"packages":[],"prev":{"headline":"Cross-Site Scripting (XSS) vulnerability in SAP BusinessObjects Web Intelligence","id":"CVE-2023-42474"},"products":["SAP S/4HANA Core"],"published":"2023-10-10","related":[{"cvss_score":8.1,"headline":"File upload in SAP S/4HANA","id":"CVE-2022-22530","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":8.1,"headline":"File upload in SAP S/4HANA","id":"CVE-2022-22531","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":6.5,"headline":"Missing authorization in S/4 HANA (Map Treasury Correspondence Format Data)","id":"CVE-2023-24524","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":6.5,"headline":"Information disclosure in SAP S/4HANA (Supplier Factsheet and Enterprise Search for Business Partner, Supplier and Customer)","id":"CVE-2022-22542","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":6.1,"headline":"URL Redirection vulnerability in SAP S/4HANA (Manage Catalog Items and Cross-Catalog search)","id":"CVE-2023-40306","kev_date_added":null,"published":"2023-09-08"},{"cvss_score":5.4,"headline":"Missing Authorization Check In S/4HANA (Manage Withholding Tax Items)","id":"CVE-2023-42473","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":5.4,"headline":"Missing authorization in SAP S/4HANA","id":"CVE-2022-31597","kev_date_added":null,"published":"2022-07-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-09-28","vendors":["SAP_SE"]},"summary":"A low-privileged attacker can read server files due to a vulnerable file storage location in the Statutory Reporting application.","url":"https://insights.sbomify.com/CVE-2023-42475/"}