{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-0530 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0530 is a medium-severity vulnerability in n/a, published on 21 Jan 2016. 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-2016-0530 and fix it if it is affected.\n\nWhat it is: CVE-2016-0530 is a medium-severity vulnerability in n/a, published on 21 Jan 2016. 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-2016-0530 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-0530/ (Markdown: https://insights.sbomify.com/CVE-2016-0530/index.md)","id":"CVE-2016-0530","markdown":"https://insights.sbomify.com/CVE-2016-0530/index.md","name":"CVE-2016-0530","record":{"aliases":["GHSA-f6hm-pf3c-83r3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle E-Business Suite","requires_auth":"low_privilege","summary":"Remote attackers can compromise confidentiality and integrity in Oracle E-Business Suite via the Customer Interaction History component.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"customer_interaction_history","vendor":"oracle"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in the Oracle Customer Interaction History component in Oracle E-Business Suite 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, and 12.2.5 allows remote attackers to affect confidentiality and integrity via vectors related to User GUI, a different vulnerability than CVE-2016-0527, CVE-2016-0528, and CVE-2016-0529.","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":"Other in n/a","id":"CVE-2016-0530","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2016-0531"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2016-0529"},"products":["n/a"],"published":"2016-01-21","related":[{"cvss_score":8.2,"headline":"Information disclosure in Customer Interaction History","id":"CVE-2021-2105","kev_date_added":null,"published":"2021-01-20"},{"cvss_score":8.2,"headline":"Information disclosure in Customer Interaction History","id":"CVE-2021-2106","kev_date_added":null,"published":"2021-01-20"},{"cvss_score":8.2,"headline":"Information disclosure in Customer Interaction History","id":"CVE-2021-2107","kev_date_added":null,"published":"2021-01-20"},{"cvss_score":8.2,"headline":"Cross-site scripting in Customer Interaction History","id":"CVE-2020-2873","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":8.2,"headline":"Cross-site scripting in Customer Interaction History","id":"CVE-2018-3189","kev_date_added":null,"published":"2018-10-17"},{"cvss_score":8.2,"headline":"Missing authorization in Customer Interaction History","id":"CVE-2017-3440","kev_date_added":null,"published":"2017-01-27"},{"cvss_score":8.2,"headline":"Cross-site scripting in Customer Interaction History","id":"CVE-2017-3441","kev_date_added":null,"published":"2017-01-27"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can compromise confidentiality and integrity in Oracle E-Business Suite via the Customer Interaction History component.","url":"https://insights.sbomify.com/CVE-2016-0530/"}