SSL alerts.

.

xml/alerts/ssl-anonymous-dh.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Anonymous Diffie-Hellman Supported</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+	<impact>Clients connecting with anonymous Diffie-Hellman are susceptible to MITM attacks.</impact>
+
+	<remediation>
+		For deployments using OpenSSL, Anonymous Diffie-Hellman can be disabled by adding "!ADH" to the supported cipher list string.
+	</remediation>
+	<remediation>
+		The HTTPS server should be restarted after such a change.
+	</remediation>
+
+	<discussion>
+		Diffie-Hellman is a key-agreement protocol that is used by clients and servers to mutually derive a session key for the HTTPS session. Anonymous Diffie-Hellman is a version without authentication. Vega detected support for anonymous Diffie-Hellman offered by the server.
+	</discussion>
+
+	<references>
+		<url address="http://wiki.openssl.org/index.php/Diffie_Hellman">Diffie-Hellman (OpenSSL)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-client-preference.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Client Ciphersuite Preference</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+	<impact>User browsers may select less secure cipher suites creating opportunities for attack.</impact>
+
+	<remediation>
+		HTTPS server should be configured to enforce server ciphersuite preferences. How this is configured will vary by server.
+	</remediation>
+	<remediation>
+		Mozilla has included guidelines for configuring server ciphersuite preference for various implementations. See link below.
+	<discussion>
+		The server can override client ciphersuite prioritization during the TLS handshake. This is useful for enforcing better, more
+		secure ciphersuites for all visiting clients. Vega has detected that this is not configured in the server, potentially leaving
+		older clients at risk.
+	</discussion>
+
+	<references>
+		<url address="https://wiki.mozilla.org/Security/Server_Side_TLS"> Server Side TLS (Mozilla)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-compression.xml

@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>TLS Compression Support (CRIME attack)</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+	<impact>Attackers may be able to exploit the CRIME attack to obtain session cookies or other sensitive data.</impact>
+
+	<remediation>
+		TLS Compression can be disabled in the server configuration. Consult documentation for the precise steps.
+	</remediation>
+	<remediation>
+		The Mozilla Server Side TLS configuration guide includes instructions for disabling TLS/SSL compression in server configuration (see link below).
+	</remediation>
+	<remediation> 
+		The HTTPS server must likely be restarted for configuration changes to take effect.
+	</remediation>
+
+	<discussion>
+		Vega detected that TLS compression is enabled by the server. This can be leveraged to carry out a chosen-plaintext attack through observing the compression ratio of data sent back from the server. If the attacker can induce a target user into making specific requests, it may be possible for them to obtain their session cookie.
+	</discussion>
+
+	<references>
+                <url address="https://wiki.mozilla.org/Security/Server_Side_TLS"> Server Side TLS (Mozilla)</url>
+		<url address="http://en.wikipedia.org/wiki/CRIME">CRIME attack against TLS</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-export-ciphers.xml

@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Export Grade Ciphers Supported</title>
+
+	<class>Configuration</class>
+
+	<severity>Low</severity>
+
+	<impact>Export grade ciphers do not offer a strong level of security.</impact>
+
+	<remediation>
+		For implemented using OpenSSL, "!EXPORT" can be added to the supported ciphersuites string to disable support for export grade ciphers.
+	</remediation>
+        <remediation>
+                The Mozilla Server Side TLS configuration guide includes instructions for disabling spport for export grade ciphers in server configuration (see link below).
+        </remediation>
+	<remediation>
+		The HTTPS server should be restarted after such a change is made.
+	</remediation>
+
+
+	<discussion>
+		Vega detected server support for weak ("export grade") cipher suites.
+	</discussion>
+
+	<references>
+                <url address="https://wiki.mozilla.org/Security/Server_Side_TLS"> Server Side TLS (Mozilla)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-md5-cert.xml

@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Certificate signed using MD5</title>
+
+	<class>Configuration</class>
+
+	<severity>High</severity>
+
+	<impact>Certificates may be forged.</impact>
+	<impact>Forged certificatescan be used in MITM attacks against users.</impact>
+
+	<remediation>
+		Obtain a new certificate signed with SHA-256.
+	</remediation>
+
+
+	<discussion>
+		Vega detected a certificate signed using MD5. MD5 is known to be insecure, and this has been demonstrated with known certificate forgery.
+	</discussion>
+
+	<references>
+		<url address="http://en.wikipedia.org/wiki/MD5#Collision_vulnerabilities">MD5 Collision Vulnerabilities (Wikipedia)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-no-pfs.xml

@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Forward Secrecy Not Supported</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+        <impact>If a forward secret cipher is not used, the security of the session data is as secure as the server's long-term private key.</impact>
+
+        <remediation>
+                Server administrators should configure the server to prioritize forward secret cipher suites such as those using ECDHE (elliptic-curve DH ephemeral) and DHE (DH ephemeral).
+        </remediation>
+        <remediation>
+                Mozilla has made guielines available for securely configuring TLS servers. See the references section for a link.
+        </remediation>
+        <remediation>
+                The HTTPS server must likely be restarted for any configuration changes to take effect.
+        </remediation>
+
+        <discussion>
+                Vega detected that the server does not support or prioritize forward secret ciphers in the list of supported cipher suites.
+                Forward secret ciphers use algorithms such as Diffie-Hellman ephemeral to generate a single-use session key. This key
+                is not derived from the long-term private key, therefore the security of the data is not subject to decryption if that key
+                is compromised in the future.
+        </discussion>
+
+        <references>
+                <url address="https://wiki.mozilla.org/Security/Server_Side_TLS">Security/Server Side TLS (Mozilla)</url>
+                <url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+        </references>
+
+
+</alert>
+

xml/alerts/ssl-pfs-not-preferred.xml

@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Forward Secrecy Not Prioritized</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+	<impact>If a forward secret cipher is not used, the security of the session data is as secure as the server's long-term private key.</impact>
+
+	<remediation>
+		Server administrators should configure the server to prioritize forward secret cipher suites such as those using ECDHE (elliptic-curve DH ephemeral) and DHE (DH ephemeral).
+	</remediation>
+	<remediation>
+		Mozilla has made guielines available for securely configuring TLS servers. See the references section for a link.
+	</remediation>
+	<remediation>
+		The HTTPS server must likely be restarted for any configuration changes to take effect.
+	</remediation>
+
+	<discussion>
+		Vega detected that the server does not prioritize forward secret ciphers in the list of supported cipher suites.
+		Forward secret ciphers use algorithms such as Diffie-Hellman ephemeral to generate a single-use session key. This key
+		is not derived from the long-term private key, therefore the security of the data is not subject to decryption if that key
+		is compromised in the future. 
+	</discussion>
+
+	<references>
+		<url address="https://wiki.mozilla.org/Security/Server_Side_TLS">Security/Server Side TLS (Mozilla)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-rc4-preference.xml

@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>RC4 Preferred Cipher</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+	<impact>RC4 has known weaknesses and may be found to be broken in the future.</impact>
+	<impact>Data confidentiality may be at risk.</impact>
+
+	<remediation>
+		RC4 should not be prioritized as the most preferred cipher by the server.
+	</remediation>
+	<remediation>
+		This can be changed in the server configuration settings. Mozilla has guidelines on server-side TLS configuration for a number of implementations. See link below.
+	</remediation>
+	<remediation>
+		The HTTPS server would likely need to be restarted for configuration changes to take effect.
+	</remediation>
+
+	<discussion>
+		Vega detected RC4 as a cipher prioritized by the vendor. RC4 has known issues and it is suspected that even more severe vulnerabilities may be unknown publicly. It is recommended that more secure ciphers be prioritized by the server. Consult the guidance provided by Mozilla in their Server Side TLS configuration guide.
+	</discussion>
+
+	<references>
+                <url address="https://wiki.mozilla.org/Security/Server_Side_TLS"> Server Side TLS (Mozilla)</url>
+		<url address="http://en.wikipedia.org/wiki/RC4#Biased_outputs_of_the_RC4">Biased outputs of the RC4 (Wikipedia)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-self-signed.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Self-Signed Certificate</title>
+
+	<class>Configuration</class>
+
+	<severity>Info</severity>
+
+	<impact>This is an informational finding.</impact>
+
+	<remediation>
+		N/A.
+	</remediation>
+
+
+	<discussion>
+		Vega detected a self-signed certificate.
+	</discussion>
+
+	<references>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-sha1-cert.xml

@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Certificate signed using SHA-1</title>
+
+	<class>Configuration</class>
+
+	<severity>Medium</severity>
+
+	<impact>Certificates can be forged by capable adversaries.</impact>
+	<impact>Forged certificates can be used in MITM attacks against connecting clients.</impact>
+
+	<remediation>
+		Renew certificates with SHA-256 signatures.
+	</remediation>
+	<remediation>
+		This should be done before 2016.
+	</remediation>
+
+	<discussion>
+		Vega detected a certificate signed using SHA-1. SHA-1 is a hash algorithm used in digital signatures. It is currently considered deprecated due to the increasing feasibility in breaking it. 
+	</discussion>
+
+	<references>
+		<url address="http://en.wikipedia.org/wiki/SHA-1">SHA-1 (Wikipedia)</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-small-key.xml

@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>Small RSA Modulus</title>
+
+	<class>Configuration</class>
+
+	<severity>High</severity>
+
+	<impact>Data security may be at risk.</impact>
+	<impact>Users may be vulnerable to data decryption or MITM attacks.</impact>
+
+	<remediation>
+		Deploy with an RSA key with a larger modulus (2048 recommended).
+	</remediation>
+
+	<discussion>
+		Vega detected a 1024 bit or smaller RSA public key. This is unacceptably small today and may be vulnerable to factorization.
+	</discussion>
+
+	<references>
+		<url address="http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29">RSA Cryptosystem</url>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+

xml/alerts/ssl-v2-support.xml

@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<alert>
+<title>SSLv2 Support</title>
+
+	<class>Configuration</class>
+
+	<severity>High</severity>
+
+	<impact>SSLv2 is vulnerable to many known attacks that can affect user security.</impact>
+
+	<remediation>
+		Support for SSLv2 should be disabled as it is obsolete.
+	</remediation>
+	<remediation>
+                The Mozilla Server Side TLS configuration guide includes instructions for disabling SSLv2 in server configuration (see link below).
+        </remediation>
+	<remediation>
+		It is likely that the HTTPS server must be restarted for configuration changes to take effect.
+	</remediation>
+
+	<discussion>
+		Vega discovered support for SSLv2. SSLv2 is known to have many serious vulnerabilities and should not be supported or used.
+	</discussion>
+
+	<references>
+        	<url address="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS (Wikipedia)</url>
+	</references>
+
+</alert>
+