Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Exploitation test by Anon-Ninja-Cat <3 see Cone-Ninja-Cat for Clearance - who will see Infosec-Ninja-Cat to Access the Cyber-Hive / Beware of Ghost-Ninja-Cat Tracking the Connections :)
- #OpDeathEaters
- #OpChemtrails
- We Are Anonymous
- We Are Legion
- We Are Ghosts of The Cyber-Hive
- We Own The Matrix...
- May Your Hacking Be Legendary Anon Family <3
- http://www.royal.gov.uk/
- IP Address 69.172.200.184
- Server Type nginx/1.7.6
- 69.172.200.184
- Server:nginx/1.7.6
- IP Address:69.172.200.184
- Port:443
- Hostname:www.royal.gov.uk
- scan report for 69.172.200.184
- Host is up (0.039s latency).
- PORT STATE SERVICE
- 80/tcp open http
- 443/tcp open https
- HTTP/1.1 200 OK
- Server: nginx/1.7.6
- Date: Mon, 05 Jan 2015 07:37:52 GMT
- Content-Type: text/html
- Connection: close
- P3P: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
- Cache-Control: no-cache
- IP Address Location IP Address Owner Last seen on this IP
- 69.172.200.184 Richmond - Canada Peer 1 Network (USA) Inc. 2015-01-02
- 0 site(s) hosted on ip 69.172.200.184
- Location: New York,United States
- ----- www.royal.gov.uk -----
- Host's addresses:
- __________________
- www.royal.gov.uk 5 IN A 69.172.200.184
- royal.gov.uk 69.172.200.184 US,UNITED STATES mail.royal.gov.uk gov.uk
- The URL "http://www.royal.gov.uk/" has the following allowed methods: *, GET, HEAD.
- The mail account: "[email protected]" was found in: "http://www.google.com/[email protected]&start=10&sa=N&hl=en".
- The remote web server seems to have a reverse proxy installed
- The remote web server sent the HTTP header: "P3P" with value: "CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"".
- The target site *has* a DNS wildcard configuration
- The remote network has an active filter.
- ==================================================================================================================================
- Testing SSL server www.royal.gov.uk on port 443
- Supported Server Cipher(s):
- Accepted TLSv1 256 bits AES256-SHA
- Accepted TLSv1 128 bits AES128-SHA
- Accepted TLSv1 168 bits DES-CBC3-SHA
- Accepted TLSv1 128 bits RC4-SHA
- Prefered Server Cipher(s):
- TLSv1 128 bits RC4-SHA
- SSL Certificate:
- Version: 2
- Serial Number: 1277064306
- Signature Algorithm: sha1WithRSAEncryption
- Issuer: /C=US/O=Entrust, Inc./OU=www.entrust.net/rpa is incorporated by reference/OU=(c) 2009 Entrust, Inc./CN=Entrust Certification Authority - L1C
- Not valid before: Dec 3 17:24:17 2012 GMT
- Not valid after: Dec 12 03:22:29 2016 GMT
- Subject: /C=GB/L=London/O=The Royal Household/OU=Information Systems Management/CN=www.royal.gov.uk
- Public Key Algorithm: rsaEncryption
- RSA Public Key: (2048 bit)
- Modulus (2048 bit):
- 00:ed:82:86:db:0f:7b:9a:0c:a3:1a:3c:e5:91:4b:
- e8:ad:66:6b:85:35:7d:96:c1:5c:32:34:3f:b0:27:
- 75:86:60:f0:f1:c3:f3:99:cf:db:f7:5a:a2:9b:fc:
- d2:3e:c3:d8:4f:ec:58:45:fc:f6:f5:2c:5f:a8:44:
- 9b:25:b3:34:90:57:f6:b6:a4:66:9d:0e:21:4d:cb:
- 53:5e:27:05:d5:c1:d5:f5:82:60:03:72:36:31:73:
- fd:f3:5e:71:70:d3:9b:9e:20:02:4f:1c:ad:ee:95:
- 80:f3:b7:06:fb:04:87:42:f2:50:71:38:f0:e5:4c:
- d0:52:87:be:d3:e9:f8:69:ba:ff:75:74:1b:c6:c6:
- 41:4c:70:21:65:0c:9f:10:d9:ec:7f:ef:56:4c:11:
- 64:42:d0:dd:2e:ba:b6:2a:99:8e:f3:d7:4c:e6:e6:
- 8c:f4:c0:ee:37:bd:2a:c2:a0:f0:a0:81:d5:64:b5:
- 1a:62:a2:b9:da:43:a3:f6:70:e0:dd:c0:18:59:00:
- a7:c7:a3:40:c9:ba:8d:2f:02:5d:ea:1b:a2:84:f4:
- f4:0d:33:be:53:ad:d4:3e:2d:d1:b8:a3:49:5a:e1:
- 97:de:e7:cf:44:5e:49:93:13:34:bd:fe:ec:07:32:
- cb:bd:ae:71:f9:11:60:8e:43:ae:39:f3:a4:ea:33:
- 57:3d
- Exponent: 65537 (0x10001)
- X509v3 Extensions:
- X509v3 Key Usage:
- Digital Signature, Key Encipherment
- X509v3 Extended Key Usage:
- TLS Web Server Authentication
- X509v3 CRL Distribution Points:
- URI:http://crl.entrust.net/level1c.crl
- Authority Information Access:
- OCSP - URI:http://ocsp.entrust.net
- CA Issuers - URI:http://aia.entrust.net/2048-l1c.cer
- X509v3 Certificate Policies:
- Policy: 1.2.840.113533.7.75.2
- CPS: http://www.entrust.net/rpa
- Policy: 2.23.140.1.2.2
- X509v3 Subject Alternative Name:
- DNS:www.royal.gov.uk
- X509v3 Authority Key Identifier:
- keyid:1E:F1:AB:89:06:F8:49:0F:01:33:77:EE:14:7A:EE:19:7C:93:28:4D
- X509v3 Subject Key Identifier:
- 71:62:B5:4C:E1:E8:91:0B:F7:E4:22:EA:03:D7:F2:42:F6:33:36:DD
- X509v3 Basic Constraints:
- EXPLOITS:
- The whole target has no protection (X-Frame-Options header) against ClickJacking attack
- A web backdoor was found at: "http://www.royal.gov.uk/ListServlet"; this could indicate that the server was hacked. ( i think so )(lulz)
- GET http://www.royal.gov.uk/ListServlet HTTP/1.1
- Host: www.royal.gov.uk
- The URL: "http://www.royal.gov.uk/ListServlet" sent the cookie: "ASP.NET_SessionId=erj2g245yzjyjbqz2y0uh055; path=/; HttpOnly"
- GET http://www.royal.gov.uk/ListServlet HTTP/1.1
- Host: www.royal.gov.uk
- A cookie matching the cookie fingerprint DB has been found when requesting "http://www.royal.gov.uk/ListServlet" . The remote platform is: "ASP.NET"
- The URI: "http://www.royal.gov.uk/ListServlet" sent a META tag with attribute value "version" which looks interesting.
- Server does not have session resumption enabled
- Users may experience slower performance
- Server has not enabled HTTP Strict-Transport-Security
- Users may be exposed to man-in-the-middle attacks
- Server doesn’t prefer ciphers that enable forward secrecy.
- Encrypted communications captured today are at risk of being decrypted by an attacker in the future
- Server uses RC4 cipher with modern browsers
- More secure ciphers are available for TLS 1.1 and newer
- Server is using RC4-based ciphersuites which have known vulnerabilities
- Evaluate your client compatibility requirements to determine if you can disable RC4-based ciphersuites
- SSL 2.0 Disabled:Pass
- SSL 3.0 Disabled:Pass
- TLS 1.0 Enabled:Pass
- TLS 1.1 Enabled:Pass
- TLS 1.2 Enabled:Pass
- Weak ciphersuites disabled:Pass
- Certificates configured correctly:Pass
- Secure renegotiation configured:Pass
- Session resumption configured:Fail
- BEAST Vulnerability:Pass
- OCSP Stapling:Fail
- PCI Compliant:Pass
- FIPS Compliant:Fail
- Forward Secrecy Supported:Fail
- Heartbleed Vulnerability:Pass
- Strict Transport Security:Fail
- Mixed Content (HTTP and HTTPS):Pass
- Domain name resolves to IPv4 address:Pass
- Domain name resolves to IPv6 address:Fail
Add Comment
Please, Sign In to add comment