{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2016-0270 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0270 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0270 is a medium-severity vulnerability in n/a, published on 8 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-0270 and fix it if it is affected.\n\nWhat it is: CVE-2016-0270 is a medium-severity vulnerability in n/a, published on 8 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-0270 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-0270/ (Markdown: https://insights.sbomify.com/CVE-2016-0270/index.md)","id":"CVE-2016-0270","markdown":"https://insights.sbomify.com/CVE-2016-0270/index.md","name":"CVE-2016-0270","record":{"aliases":["GHSA-vxq9-8hgp-5mw5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"IBM Domino server","requires_auth":"none","summary":"Remote attackers can obtain authentication keys and spoof data in IBM Domino when TLS AES GCM is used due to nonce reuse vulnerabilities.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"client_application_access","vendor":"ibm"},{"product":"domino","vendor":"ibm"},{"product":"notes","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Domino 9.0.1 Fix Pack 3 Interim Fix 2 through 9.0.1 Fix Pack 5 Interim Fix 1, when using TLS and AES GCM, uses random nonce generation, which makes it easier for remote attackers to obtain the authentication key and spoof data by leveraging the reuse of a nonce in a session and a \"forbidden attack.\" NOTE: this CVE has been incorrectly used for GCM nonce reuse issues in other products; see CVE-2016-10213 for the A10 issue, CVE-2016-10212 for the Radware issue, and CVE-2017-5933 for the Citrix issue.","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":"Weak cryptography in n/a","id":"CVE-2016-0270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2016"},"n_packages":0,"n_references":7,"next":{"headline":"Auth bypass in n/a","id":"CVE-2016-0271"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2016-0269"},"products":["n/a"],"published":"2017-02-08","related":[{"cvss_score":7.8,"headline":"Command injection in Client Application Access","id":"CVE-2018-1409","kev_date_added":null,"published":"2018-02-19"},{"cvss_score":7.8,"headline":"Command injection in Client Application Access","id":"CVE-2018-1410","kev_date_added":null,"published":"2018-02-19"},{"cvss_score":7.8,"headline":"Command injection in Client Application Access","id":"CVE-2018-1411","kev_date_added":null,"published":"2018-02-19"},{"cvss_score":7.8,"headline":"Other in Client Application Access","id":"CVE-2017-1711","kev_date_added":null,"published":"2018-02-13"},{"cvss_score":7.8,"headline":"Privilege escalation in Client Application Access","id":"CVE-2017-1714","kev_date_added":null,"published":"2018-02-13"},{"cvss_score":5.3,"headline":"Command injection in Client Application Access","id":"CVE-2017-1720","kev_date_added":null,"published":"2018-02-13"}],"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":["n/a"]},"summary":"Remote attackers can obtain authentication keys and spoof data in IBM Domino when TLS AES GCM is used due to nonce reuse vulnerabilities.","url":"https://insights.sbomify.com/CVE-2016-0270/"}