{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21475 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21475 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21475 is a medium-severity vulnerability in Oracle Corporation Banking Payments, published on 19 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-21475 and fix it if it is affected.\n\nWhat it is: CVE-2022-21475 is a medium-severity vulnerability in Oracle Corporation Banking Payments, published on 19 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-21475 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-2022-21475/ (Markdown: https://insights.sbomify.com/CVE-2022-21475/index.md)","id":"CVE-2022-21475","markdown":"https://insights.sbomify.com/CVE-2022-21475/index.md","name":"CVE-2022-21475","record":{"aliases":["GHSA-h38x-gm96-rg3c"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Banking Payments","requires_auth":"low_privilege","summary":"Low-privileged attackers can modify critical data and cause partial denial of service in Oracle Banking Payments via HTTP with user interaction.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"banking_payments","vendor":"oracle"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[],"description":"Vulnerability in the Oracle Banking Payments product of Oracle Financial Services Applications (component: Infrastructure). The supported version that is affected is 14.5. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Payments. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Banking Payments accessible data as well as unauthorized read access to a subset of Oracle Banking Payments accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Banking Payments. CVSS 3.1 Base Score 5.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L).","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":"Business logic in Banking Payments","id":"CVE-2022-21475","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Java SE JDK and JRE","id":"CVE-2022-21476"},"packages":[],"prev":{"headline":"Missing authorization in Banking Trade Finance","id":"CVE-2022-21474"},"products":["Banking Payments"],"published":"2022-04-19","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-09-24","vendors":["Oracle Corporation"]},"summary":"Low-privileged attackers can modify critical data and cause partial denial of service in Oracle Banking Payments via HTTP with user interaction.","url":"https://insights.sbomify.com/CVE-2022-21475/"}