{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-2402 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-2402 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-2402 is a high-severity vulnerability in SAP HANA, published on 14 Mar 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-2402 and fix it if it is affected.\n\nWhat it is: CVE-2018-2402 is a high-severity vulnerability in SAP HANA, published on 14 Mar 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-2402 in the wild and no public exploit code.\n\nAffected product: SAP HANA. 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-2018-2402/ (Markdown: https://insights.sbomify.com/CVE-2018-2402/index.md)","id":"CVE-2018-2402","markdown":"https://insights.sbomify.com/CVE-2018-2402/index.md","name":"CVE-2018-2402","record":{"aliases":["GHSA-955r-gv79-5833"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"SAP HANA database","requires_auth":"high_privilege","summary":"Attackers with control system access can read clear-text credentials from trace files in SAP HANA capture and replay mode, leading to unauthorized data access.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"hana","vendor":"sap"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In systems using the optional capture \u0026 replay functionality of SAP HANA, 1.00 and 2.00, (see SAP Note 2362820 for more information about capture \u0026 replay), user credentials may be stored in clear text in the indexserver trace files of the control system. An attacker with the required authorizations on the control system may be able to access the user credentials and gain unauthorized access to data in the captured or target 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":"Information disclosure in SAP HANA","id":"CVE-2018-2402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in SAP Disclosure Management","id":"CVE-2018-2403"},"packages":[],"prev":{"headline":"XML external entity in SAP Business Process Automation (BPA) By Redwood","id":"CVE-2018-2401"},"products":["SAP HANA"],"published":"2018-03-14","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2015-7828","kev_date_added":null,"published":"2015-11-10"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2016-6143","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2016-6150","kev_date_added":null,"published":"2016-08-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-1928","kev_date_added":null,"published":"2016-01-20"},{"cvss_score":9.3,"headline":"Denial of service in n/a","id":"CVE-2016-1929","kev_date_added":null,"published":"2016-01-20"},{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2016-6144","kev_date_added":null,"published":"2016-08-05"},{"cvss_score":7.7,"headline":"Auth bypass in SAP HANA","id":"CVE-2021-21484","kev_date_added":null,"published":"2021-03-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["SAP SE"]},"summary":"Attackers with control system access can read clear-text credentials from trace files in SAP HANA capture and replay mode, leading to unauthorized data access.","url":"https://insights.sbomify.com/CVE-2018-2402/"}