Here are some potential justifications for lowering the severity of the weak cipher suites alert in Nuclei from medium to low:
- The risks associated with weak cipher suites are mainly related to interception of traffic and decryption of sensitive data in transit. This requires a man-in-the-middle position which limits the scale of potential abuse.
- For an external scan, it is difficult to determine the true impact of weak cipher suites without knowing details of the application architecture and data flows. There could be other protections in place that mitigate the risk.
- Weak cipher suites alone do not enable direct remote code execution or access to underlying resources. Additional vulnerabilities would need to be chained to result in system compromise.
- The classification of "weak" cipher suites is also subjective and changes over time. Something considered weak today may still be commonly used and considered acceptable by many organizations.
- The CVSS score ranges from none to low for interception of non-sensitive data in transit. For external scanning, it's uncertain if truly sensitive data is exposed.
- Remediation requires updating server configurations across potentially many hosts. While recommended in the long term, it is not always trivial for organizations to deploy in the short term.
- There are likely higher severity issues that should be prioritized for remediation first, rather than just the acceptable cipher suites.
While weak cipher suites are not advisable, their ease of exploitation is limited in many real-world scenarios. And when performing external testing, it's difficult to determine the true impact. Given these factors, lowering the severity rating seems reasonable compared to other more serious remote bugs. But organizations should still look to phase out weak ciphers in a responsible manner.
* Add description and enhance one where the UI failed to save properly.
dos2unix on a template
* Change cvedetails link to nvd
* make severities match
* Enhancement: cves/2015/CVE-2015-2863.yaml by md
* Enhancement: cves/2017/CVE-2017-14524.yaml by md
* Enhancement: cves/2017/CVE-2017-5638.yaml by md
* Enhancement: cves/2019/CVE-2019-16759.yaml by md
* Enhancement: cves/2021/CVE-2021-22986.yaml by md
* Enhancement: cves/2021/CVE-2021-24145.yaml by md
* Enhancement: cves/2021/CVE-2021-24145.yaml by md
* Enhancement: cves/2021/CVE-2021-24155.yaml by md
* Enhancement: cves/2021/CVE-2021-24145.yaml by md
* Enhancement: cves/2021/CVE-2021-24145.yaml by md
* Enhancement: cves/2021/CVE-2021-24347.yaml by md
* Enhancement: cves/2021/CVE-2021-25003.yaml by md
* Enhancement: cves/2021/CVE-2021-25296.yaml by md
* Enhancement: cves/2021/CVE-2021-25297.yaml by md
* Enhancement: cves/2021/CVE-2021-25296.yaml by md
* Enhancement: cves/2021/CVE-2021-25297.yaml by md
* Enhancement: cves/2021/CVE-2021-25298.yaml by md
* Enhancement: cves/2021/CVE-2021-25297.yaml by md
* Enhancement: cves/2021/CVE-2021-28151.yaml by md
* Enhancement: cves/2021/CVE-2021-30128.yaml by md
* Enhancement: cves/2022/CVE-2022-0824.yaml by md
* Enhancement: cves/2022/CVE-2022-0824.yaml by md
* Enhancement: cves/2022/CVE-2022-0885.yaml by md
* Enhancement: cves/2022/CVE-2022-21587.yaml by md
* Enhancement: cves/2022/CVE-2022-2314.yaml by md
* Enhancement: cves/2022/CVE-2022-24816.yaml by md
* Enhancement: cves/2022/CVE-2022-31499.yaml by md
* Enhancement: cves/2022/CVE-2022-21587.yaml by md
* Enhancement: cves/2021/CVE-2021-24155.yaml by md
* Enhancement: cves/2017/CVE-2017-5638.yaml by md
* Enhancement: cves/2015/CVE-2015-2863.yaml by md
* Enhancement: cves/2022/CVE-2022-33901.yaml by md
* Enhancement: cves/2022/CVE-2022-2314.yaml by md
* Enhancement: cves/2022/CVE-2022-33901.yaml by md
* Enhancement: cves/2022/CVE-2022-34753.yaml by md
* Enhancement: cves/2022/CVE-2022-39952.yaml by md
* Enhancement: cves/2022/CVE-2022-4060.yaml by md
* Enhancement: cves/2022/CVE-2022-44877.yaml by md
* Enhancement: cves/2023/CVE-2023-0669.yaml by md
* Enhancement: cves/2023/CVE-2023-26255.yaml by md
* Enhancement: cves/2023/CVE-2023-26256.yaml by md
* Enhancement: exposures/files/salesforce-credentials.yaml by md
* Enhancement: misconfiguration/hadoop-unauth-rce.yaml by md
* Enhancement: misconfiguration/installer/nopcommerce-installer.yaml by md
* Enhancement: network/backdoor/backdoored-zte.yaml by md
* Enhancement: network/detection/ibm-d2b-database-server.yaml by md
* Enhancement: network/detection/ibm-d2b-database-server.yaml by md
* Enhancement: technologies/oracle/oracle-atg-commerce.yaml by md
* Enhancement: token-spray/api-abuseipdb.yaml by md
* Enhancement: token-spray/api-abuseipdb.yaml by md
* Enhancement: token-spray/api-dbt.yaml by md
* Enhancement: vulnerabilities/avaya/avaya-aura-rce.yaml by md
* Enhancement: vulnerabilities/avaya/avaya-aura-xss.yaml by md
* Enhancement: vulnerabilities/cisco/cisco-cloudcenter-suite-rce.yaml by md
* Enhancement: vulnerabilities/froxlor-xss.yaml by md
* Enhancement: vulnerabilities/jamf/jamf-log4j-jndi-rce.yaml by md
* Enhancement: vulnerabilities/mobileiron/mobileiron-log4j-jndi-rce.yaml by md
* Enhancement: vulnerabilities/jamf/jamf-log4j-jndi-rce.yaml by md
* Enhancement: vulnerabilities/opencpu/opencpu-rce.yaml by md
* Enhancement: vulnerabilities/other/academy-lms-xss.yaml by md
* Enhancement: vulnerabilities/other/caucho-resin-info-disclosure.yaml by md
* Enhancement: vulnerabilities/other/ckan-dom-based-xss.yaml by md
* Enhancement: vulnerabilities/other/couchdb-adminparty.yaml by md
* Enhancement: vulnerabilities/other/graylog-log4j.yaml by md
* Enhancement: vulnerabilities/mobileiron/mobileiron-log4j-jndi-rce.yaml by md
* Initial cleanups for syntax errors
* dashboard gremlins
* Add log4j back to name
* Enhancement: exposures/files/salesforce-credentials.yaml by cs
* Enhancement: misconfiguration/installer/nopcommerce-installer.yaml by cs
* Enhancement: network/backdoor/backdoored-zte.yaml by cs
* Enhancement: vulnerabilities/other/couchdb-adminparty.yaml by cs
* Sev and other info tweaks
* Merge conflict
* Run dos2unix against all templates
* too many newlines error
* Fix too many blank lines error
* Fix severity mismatches
Cleanup language on a new test
---------
Co-authored-by: sullo <sullo@cirt.net>
