{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6887 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6887 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6887 is a medium-severity vulnerability in n/a, published on 13 Jan 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-6887 and fix it if it is affected.\n\nWhat it is: CVE-2016-6887 is a medium-severity vulnerability in n/a, published on 13 Jan 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-6887 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-6887/ (Markdown: https://insights.sbomify.com/CVE-2016-6887/index.md)","id":"CVE-2016-6887","markdown":"https://insights.sbomify.com/CVE-2016-6887/index.md","name":"CVE-2016-6887","record":{"aliases":["GHSA-c35w-7j4x-j365"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MatrixSSL library","requires_auth":"none","summary":"Remote attackers can predict secret keys via a CRT attack due to improper modular exponentiation in MatrixSSL.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"matrixssl","vendor":"matrixssl"}],"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":"The pstm_exptmod function in MatrixSSL 3.8.6 and earlier does not properly perform modular exponentiation, which might allow remote attackers to predict the secret key via a CRT attack.","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-6887","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2016-6888"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-6886"},"products":["n/a"],"published":"2017-01-13","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14431","kev_date_added":null,"published":"2019-07-29"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-13470","kev_date_added":null,"published":"2019-07-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-10914","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-6890","kev_date_added":null,"published":"2017-01-05"},{"cvss_score":8.1,"headline":"Integer overflow in n/a","id":"CVE-2022-43974","kev_date_added":null,"published":"2023-01-09"},{"cvss_score":8.1,"headline":"Memory corruption in MatrixSSL","id":"CVE-2017-2780","kev_date_added":null,"published":"2017-06-22"},{"cvss_score":8.1,"headline":"Memory corruption in MatrixSSL","id":"CVE-2017-2781","kev_date_added":null,"published":"2017-06-22"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can predict secret keys via a CRT attack due to improper modular exponentiation in MatrixSSL.","url":"https://insights.sbomify.com/CVE-2016-6887/"}