{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-41733 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41733 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41733 is a medium-severity vulnerability in SAP_SE SAP Commerce, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41733 and fix it if it is affected.\n\nWhat it is: CVE-2024-41733 is a medium-severity vulnerability in SAP_SE SAP Commerce, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-41733 in the wild and no public exploit code.\n\nAffected product: SAP_SE SAP Commerce. 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-41733/ (Markdown: https://insights.sbomify.com/CVE-2024-41733/index.md)","id":"CVE-2024-41733","markdown":"https://insights.sbomify.com/CVE-2024-41733/index.md","name":"CVE-2024-41733","record":{"aliases":["GHSA-4x4m-ghmx-6q9w"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP Commerce","requires_auth":"none","summary":"Attackers can identify valid user accounts via email during registration or login, revealing account existence without accessing other data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"commerce","vendor":"sap"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In SAP Commerce, valid user accounts can be\nidentified during the customer registration and login processes. This allows a\npotential attacker to learn if a given e-mail is used for an account, but does\nnot grant access to any customer data beyond this knowledge. The attacker must\nalready know the e-mail that they wish to test for. The impact on\nconfidentiality therefore is low and no impact to integrity or availability","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 SAP Commerce","id":"CVE-2024-41733","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authorization check in SAP NetWeaver Application Server ABAP and ABAP Platform","id":"CVE-2024-41734"},"packages":[],"prev":{"headline":"Improper Access Control in SAP Netweaver Application Server ABAP","id":"CVE-2024-41732"},"products":["SAP Commerce"],"published":"2024-08-13","related":[{"cvss_score":9.9,"headline":"Code injection in SAP Commerce","id":"CVE-2021-27602","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":9.9,"headline":"Code injection in SAP Commerce","id":"CVE-2021-21477","kev_date_added":null,"published":"2021-02-09"},{"cvss_score":9.8,"headline":"SQL injection in SAP Commerce","id":"CVE-2021-42064","kev_date_added":null,"published":"2021-12-14"},{"cvss_score":9.8,"headline":"Hardcoded credentials in SAP Commerce","id":"CVE-2020-6265","kev_date_added":null,"published":"2020-06-09"},{"cvss_score":8.8,"headline":"Open redirect in SAP Commerce","id":"CVE-2022-41204","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":8.8,"headline":"Missing authorization in SAP Commerce","id":"CVE-2021-40502","kev_date_added":null,"published":"2021-11-10"},{"cvss_score":8.6,"headline":"Information disclosure in SAP Commerce","id":"CVE-2020-6264","kev_date_added":null,"published":"2020-06-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":"total"},"state":"PUBLISHED","updated":"2024-08-13","vendors":["SAP_SE"]},"summary":"Attackers can identify valid user accounts via email during registration or login, revealing account existence without accessing other data.","url":"https://insights.sbomify.com/CVE-2024-41733/"}