% vary from 1 % (Hong-Kong, Singapore) to medium risk of under 45% of existing abuse.
also the web reputation of hosters/AS of such IPs should be taken into account here.
We should scan for retirable (vulnerable or left) jQuery libraries using the Retire.JS extension or online here: https://retire.insecurity.today/# (both from Erlend Oftedal)
A similar procedure should now also be undertaken for node.js also by Retire.JS because of malicious npm-packages that could open up a reverse shell like: plutov-slack-client, nodetest1010 en nodetest199 & npmpubman.
Tracker SSL - Website is insecure by default
100% of the trackers on this site could be protecting you from NSA snooping. Tell -edusantosoficial.com.br to fix it.
Identifiers | All Trackers
Insecure Identifiers
Unique IDs about your web browsing habits have been insecurely sent to third parties.
-skhXXXXXXXXXXXqjfuors7ai8tf -quiz.edusantosoficial.com.brphpsessid
Tracking IDs could be sent safely if this site was secure.
Tracking IDs do not support secure transmission. Three Content Tracking Requests from facebook
What can the above information deliver? Well insight in potentially vulnerable and sometimes exploitable code.
All depends of what security layers are available there on client and server (best policies applied)
A short partial example:
So we can scan for a vulnerability in retirable script like:
Evaluated CSP as seen by a browser supporting CSP Version 3
expand/collapse all
error default-src
error https:
https: URI in default-src allows the execution of unsafe scripts.
checkblob:
errorscript-src
error’unsafe-inline’
‘unsafe-inline’ allows the execution of unsafe in-page scripts and event handlers.
help_outline’unsafe-eval’
‘unsafe-eval’ allows the execution of code injected into DOM APIs such as eval().
error https:
https: URI in script-src allows the execution of unsafe scripts.
The web server appears to reveal version information. This can pose a security risk if vulnerabilities are identified in this version. You should consider disabling version information in your server configuration.
Here one can check all sort of files against a so-called colission attack: https://shattered.io/
The test has been developed in cooperation with the Dutch CWI (Centrum voor Wiskunde & Informatica).
Also Google developers were involved.
Within most modern browsers like Google Chrome and also inside the Firefox browser,
we have been protected against insecure TLS/SSL certificates over the last three years.
Only it is a pity that whenever you will download Firefox browser,
the signature over that particular binary still exclusively will make use of insecure SHA1.
Get the checksum from the master repro and the actual download from a fast mirror.
Normally files now come digitally signed.
Now consider the above check as a checking method against silent file corruption,
so also with a digital file signature you could check at shattered.io,
Enjoy, my good friends, enjoy,
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)
If your origin servers are exposed attackers can attack them directly and bypass any sort of protection you may have. Many large CDN companies have bad design which allows for serious security vulnerabilities.
Check your access control to guarantee a secure connection between website and webserver behind it. Or you could find yourself in such a situation, where you find direct access to
Attackers may use various special search methods on Google (so-called dorks and queries on shodan.io to find low hanging fruit on the Interwebz to compromize and worse.
Be the first party to scan, as malcreants may already have scanned you.
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)