{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3025 is a medium-severity vulnerability in Oracle Corporation Banking Payments, published on 18 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3025 and fix it if it is affected.\n\nWhat it is: CVE-2018-3025 is a medium-severity vulnerability in Oracle Corporation Banking Payments, published on 18 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-3025 in the wild and no public exploit code.\n\nAffected product: Oracle Corporation Banking Payments. 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-3025/ (Markdown: https://insights.sbomify.com/CVE-2018-3025/index.md)","id":"CVE-2018-3025","markdown":"https://insights.sbomify.com/CVE-2018-3025/index.md","name":"CVE-2018-3025","record":{"aliases":["GHSA-hf38-2r76-5mj2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Banking Payments","requires_auth":"low_privilege","summary":"A low-privileged attacker can exploit this vulnerability to gain unauthorized access to critical data within Oracle Banking Payments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"banking_payments","vendor":"oracle"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[],"description":"Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent: Payments Core). Supported versions that are affected are 12.2.0, 12.3.0, 12.4.0, 12.5.0 and 14.1.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Payments. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Banking Payments accessible data. CVSS 3.0 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N).","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 Banking Payments","id":"CVE-2018-3025","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":"Cross-site request forgery in Banking Payments","id":"CVE-2018-3026"},"packages":[],"prev":{"headline":"Missing authorization in Banking Payments","id":"CVE-2018-3024"},"products":["Banking Payments"],"published":"2018-07-18","related":[{"cvss_score":8.8,"headline":"Auth bypass in Banking Payments","id":"CVE-2018-2705","kev_date_added":null,"published":"2018-01-18"},{"cvss_score":8.1,"headline":"Missing authorization in Banking Payments","id":"CVE-2018-3027","kev_date_added":null,"published":"2018-07-18"},{"cvss_score":8.1,"headline":"Missing authorization in Banking Payments","id":"CVE-2018-2704","kev_date_added":null,"published":"2018-01-18"},{"cvss_score":7.1,"headline":"Missing authorization in Banking Payments","id":"CVE-2020-2713","kev_date_added":null,"published":"2020-01-15"},{"cvss_score":6.5,"headline":"Information disclosure in Banking Payments","id":"CVE-2020-14896","kev_date_added":null,"published":"2020-10-21"},{"cvss_score":6.5,"headline":"Information disclosure in Banking Payments","id":"CVE-2020-2711","kev_date_added":null,"published":"2020-01-15"},{"cvss_score":6.5,"headline":"Denial of service in Banking Payments","id":"CVE-2018-3022","kev_date_added":null,"published":"2018-07-18"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-02","vendors":["Oracle Corporation"]},"summary":"A low-privileged attacker can exploit this vulnerability to gain unauthorized access to critical data within Oracle Banking Payments.","url":"https://insights.sbomify.com/CVE-2018-3025/"}