{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3310 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3310 is a critical vulnerability in Oracle Database, published on 27 Jan 2017. 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-2017-3310 and fix it if it is affected.\n\nWhat it is: CVE-2017-3310 is a critical vulnerability in Oracle Database, published on 27 Jan 2017. 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-2017-3310 in the wild and no public exploit code.\n\nAffected product: Oracle Database. 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-2017-3310/ (Markdown: https://insights.sbomify.com/CVE-2017-3310/index.md)","id":"CVE-2017-3310","markdown":"https://insights.sbomify.com/CVE-2017-3310/index.md","name":"CVE-2017-3310","record":{"aliases":["GHSA-h788-pcwr-mwqf"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Database","requires_auth":"low_privilege","summary":"Low-privileged attackers can compromise the OJVM component of Oracle Database Server, leading to full takeover of the component.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"database","vendor":"oracle"}],"cvss":{"score":9,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Vulnerability in the OJVM component of Oracle Database Server. Supported versions that are affected are 11.2.0.4 and 12.1.0.2. Easily exploitable vulnerability allows low privileged attacker having Create Session, Create Procedure privilege with network access via multiple protocols to compromise OJVM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in OJVM, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of OJVM. CVSS v3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts).","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":"Privilege escalation in Oracle Database","id":"CVE-2017-3310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:database","products":["oracle:database"],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in Application Testing Suite","id":"CVE-2017-3311"},"packages":[],"prev":{"headline":"Denial of service in MySQL Server","id":"CVE-2017-3309"},"products":["Oracle Database"],"published":"2017-01-27","related":[{"cvss_score":9.9,"headline":"Privilege escalation in Oracle Database","id":"CVE-2017-10202","kev_date_added":null,"published":"2017-08-08"},{"cvss_score":9,"headline":"Other in n/a","id":"CVE-2016-3609","kev_date_added":null,"published":"2016-07-21"},{"cvss_score":9,"headline":"Other in n/a","id":"CVE-2016-3454","kev_date_added":null,"published":"2016-04-21"},{"cvss_score":8.8,"headline":"Privilege escalation in Database - Enterprise Edition","id":"CVE-2022-21510","kev_date_added":null,"published":"2022-07-19"},{"cvss_score":8.8,"headline":"Privilege escalation in Oracle Database","id":"CVE-2017-10321","kev_date_added":null,"published":"2017-10-19"},{"cvss_score":8.2,"headline":"Privilege escalation in Oracle Database","id":"CVE-2019-2619","kev_date_added":null,"published":"2019-04-23"}],"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":"total"},"state":"PUBLISHED","updated":"2024-10-08","vendors":["Oracle"]},"summary":"Low-privileged attackers can compromise the OJVM component of Oracle Database Server, leading to full takeover of the component.","url":"https://insights.sbomify.com/CVE-2017-3310/"}