4.0

More documents

Recommendations

Info

162Web Application Penetration TestingExample 4 Checking for Client-initiated Renegotiation and SecureRenegotiation via openssl (manually)Openssl [30] can be used for testing manually SSL/TLS. In thisexample the tester tries to initiate a renegotiation by client [m]connecting to server with openssl. The tester then writes the fistline of an HTTP request and types “R” in a new line. He then waitsfor renegotiaion and completion of the HTTP request and checksif secure renegotiaion is supported by looking at the server output.Using manual requests it is also possible to see if Compressionis enabled for TLS and to check for CRIME [13], for ciphersand for other vulnerabilities.$ openssl s_client -connect www2.example.com:443CONNECTED(00000003)depth=2 ******verify error:num=20:unable to get local issuer certificateverify return:0---Certificate chain0 s:******i:******1 s:******i:******2 s:******i:******---Server certificate-----BEGIN CERTIFICATE-----******-----END CERTIFICATE-----subject=******issuer=******---No client certificate CA names sent---SSL handshake has read 3558 bytes and written 640 bytes---New, TLSv1/SSLv3, Cipher is DES-CBC3-SHAServer public key is 2048 bitSecure Renegotiation IS NOT supportedCompression: NONEExpansion: NONESSL-Session:Protocol : TLSv1Cipher : DES-CBC3-SHASession-ID: ******Session-ID-ctx:Master-Key: ******Key-Arg : NonePSK identity: NonePSK identity hint: NoneSRP username: NoneStart Time: ******Timeout : 300 (sec)Verify return code: 20 (unable to get local issuer certificate)---Now the tester can write the first line of an HTTP request andthen R in a new line.HEAD / HTTP/1.1RServer is renegotiatingRENEGOTIATINGdepth=2 C******verify error:num=20:unable to get local issuer certificateverify return:0And the tester can complete our request, checking for response.Even if the HEAD is not permitted, Client-intiated renegotiaionis permitted.HEAD / HTTP/1.1HTTP/1.1 403 Forbidden ( The server denies the specified UniformResource Locator (URL). Contact the server administrator. )Connection: closePragma: no-cacheCache-Control: no-cacheContent-Type: text/htmlContent-Length: 1792read:errno=0Example 5. Testing supported Cipher Suites, BEAST and CRIMEattacks via TestSSLServerTestSSLServer [32] is a script which permits the tester to checkthe cipher suite and also for BEAST and CRIME attacks. BEAST(Browser Exploit Against SSL/TLS) exploits a vulnerability ofCBC in TLS 1.0. CRIME (Compression Ratio Info-leak Made Easy)exploits a vulnerability of TLS Compression, that should be disabled.What is interesting is that the first fix for BEAST was theuse of RC4, but this is now discouraged due to a crypto-analyticalattack to RC4 [15].An online tool to check for these attacks is SSL Labs, but can be usedonly for internet facing servers. Also consider that target data will bestored on SSL Labs server and also will result some connection fromSSL Labs server [21].$ java -jar TestSSLServer.jar www3.example.com 443Supported versions: SSLv3 TLSv1.0 TLSv1.1 TLSv1.2Deflate compression: noSupported cipher suites (ORDER IS NOT SIGNIFICANT):SSLv3RSA_WITH_RC4_128_SHARSA_WITH_3DES_EDE_CBC_SHADHE_RSA_WITH_3DES_EDE_CBC_SHARSA_WITH_AES_128_CBC_SHADHE_RSA_WITH_AES_128_CBC_SHA
163Web Application Penetration TestingRSA_WITH_AES_256_CBC_SHADHE_RSA_WITH_AES_256_CBC_SHARSA_WITH_CAMELLIA_128_CBC_SHADHE_RSA_WITH_CAMELLIA_128_CBC_SHARSA_WITH_CAMELLIA_256_CBC_SHADHE_RSA_WITH_CAMELLIA_256_CBC_SHATLS_RSA_WITH_SEED_CBC_SHATLS_DHE_RSA_WITH_SEED_CBC_SHA(TLSv1.0: idem)(TLSv1.1: idem)TLSv1.2RSA_WITH_RC4_128_SHARSA_WITH_3DES_EDE_CBC_SHADHE_RSA_WITH_3DES_EDE_CBC_SHARSA_WITH_AES_128_CBC_SHADHE_RSA_WITH_AES_128_CBC_SHARSA_WITH_AES_256_CBC_SHADHE_RSA_WITH_AES_256_CBC_SHARSA_WITH_AES_128_CBC_SHA256RSA_WITH_AES_256_CBC_SHA256RSA_WITH_CAMELLIA_128_CBC_SHADHE_RSA_WITH_CAMELLIA_128_CBC_SHADHE_RSA_WITH_AES_128_CBC_SHA256DHE_RSA_WITH_AES_256_CBC_SHA256RSA_WITH_CAMELLIA_256_CBC_SHADHE_RSA_WITH_CAMELLIA_256_CBC_SHATLS_RSA_WITH_SEED_CBC_SHATLS_DHE_RSA_WITH_SEED_CBC_SHATLS_RSA_WITH_AES_128_GCM_SHA256TLS_RSA_WITH_AES_256_GCM_SHA384TLS_DHE_RSA_WITH_AES_128_GCM_SHA256TLS_DHE_RSA_WITH_AES_256_GCM_SHA384----------------------Server certificate(s):******----------------------Minimal encryption strength: strong encryption (96-bit ormore)Achievable encryption strength: strong encryption (96-bit ormore)BEAST status: vulnerableCRIME status: protectedExample 6. Testing SSL/TLS vulnerabilities with sslyzeSslyze [33] is a python script which permits mass scanning and XMLoutput. The following is an example of a regular scan. It is one of themost complete and versatile tools for SSL/TLS testing./sslyze.py --regular example.com:443REGISTERING AVAILABLE PLUGINS-----------------------------PluginHSTSPluginSessionRenegotiationPluginCertInfoPluginSessionResumptionPluginOpenSSLCipherSuitesPluginCompressionCHECKING HOST(S) AVAILABILITY-----------------------------example.com:443 => 127.0.0.1:443SCAN RESULTS FOR EXAMPLE.COM:443 - 127.0.0.1:443---------------------------------------------------* Compression :Compression Support:Disabled* Session Renegotiation :Client-initiated Renegotiations: RejectedSecure Renegotiation: Supported* Certificate :Validation w/ Mozilla’s CA Store: Certificate is NOT Trusted:unable to get local issuer certificateHostname Validation: MISMATCHSHA1 Fingerprint: ******Common Name:www.example.comIssuer: ******Serial Number: ****Not Before:Sep 26 00:00:00 2010 GMTNot After:Sep 26 23:59:59 2020 GMTSignature Algorithm: sha1WithRSAEncryptionKey Size:1024 bitX509v3 Subject Alternative Name: {‘othername’: [‘’],‘DNS’: [‘www.example.com’]}* OCSP Stapling :Server did not send back an OCSP response.* Session Resumption :With Session IDs: Supported (5 successful, 0 failed,0 errors, 5 total attempts).With TLS Session Tickets: Supported* SSLV2 Cipher Suites :Rejected Cipher Suite(s): Hidden
Page 1 and 2:
1Testing Guide4.0Project Leaders: M
Page 3 and 4:
Testing Guide Foreword - Table of c
Page 5 and 6:
3Testing Guide Foreword - Table of
Page 7 and 8:
5Testing Guide Foreword - By Eoin K
Page 9 and 10:
7Testing Guide Frontispiece1Testing
Page 11 and 12:
9Testing Guide Introduction2The OWA
Page 13 and 14:
11Testing Guide Introductionvide en
Page 15 and 16:
13Testing Guide IntroductionTesting
Page 17 and 18:
15Testing Guide Introductionlaid on
Page 19 and 20:
17Testing Guide Introductionvalidat
Page 21 and 22:
19Testing Guide IntroductionUSERthe
Page 23 and 24:
21Testing Guide Introductionment wh
Page 25 and 26:
23Testing Guide Introductionoffendi
Page 27 and 28:
25The OWASP Testing Frameworksectio
Page 29 and 30:
27Web Application Penetration Testi
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
101Web Application Penetration Test
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114: 111Web Application Penetration Test
Page 163: 161Web Application Penetration Test
Page 211 and 212: 209same code can be applied to sess
Page 213 and 214: 211ReportingTest IDLowest versionIn
Page 215 and 216:
213ReportingTest IDBusiness Logic T
Page 217 and 218:
215Appendixkajfghlhfkcocafkcjlajldi
Page 219 and 220:
217AppendixTesting - http:/www.nist
Page 221 and 222:
219Cross Site Scripting (XSS)For de
Page 223 and 224:
221LDAP InjectionFor details on LDA
show all

4.0

Create successful ePaper yourself

Delete template?

Save as template?