Avast WEBforum
Other => Viruses and worms => Topic started by: REDACTED on March 31, 2016, 07:41:11 PM
-
Bonjour,
Avast say that neo-net.fr is a malware URL. But, this is false because I'm on this forum and I know the Administrator. There are no viruses in programs, ... It's a false positive. Can you correct this ?
Thank you
-
URL:Mal = Blacklisted URL or IP
IP history > https://virustotal.com/en/ip-address/213.186.33.19/information/
https://virustotal.com/en/url/ff5fa70415e32550a6f72a0d685a907048603f93648b8da96a4ebac31b5c5506/analysis/1459446265/
Sucuri > https://sitecheck.sucuri.net/results/neo-net.fr
Norton SafeWeb > https://safeweb.norton.com/report/show?url=neo-net.fr
Threat Name: PUA.OpenCandy
Location: hxxp://download.freemake.net/FreemakeOriginals2/FreemakeVideoDownloaderSetup.exe
https://virustotal.com/en/file/131e7e46ee189bbb8fa5ce51f4cfe8b558416c1cb486f34266686645e79db622/analysis/1459446525/
Threat Name: Direct Link To PUA.OpenCandy
Location: hxxp://neo-net.fr/forum/tel/tel/ZedTV.exe
File seems to be removed
-
Suspicious :
https://www.virustotal.com/en/url/ff5fa70415e32550a6f72a0d685a907048603f93648b8da96a4ebac31b5c5506/analysis/1459446265/
Blacklisted, linking to blacklisted site and likely infected :
http://zulu.zscaler.com/submission/show/3dfec722663d83dec675ae5a1d190bb9-1459446218
Linking to blacklisted and likelu infected website(s) :
http://www.web-malware-removal.com/website-malware-virus-scanner/?url=neo-net.fr
Blacklisted and infected :
https://sitecheck.sucuri.net/results/neo-net.fr
https://safeweb.norton.com/report/show?url=neo-net.fr
Blacklisted :
http://urlquery.net/report.php?id=1459446629068
http://urlquery.net/report.php?id=1459446624737
http://multirbl.valli.org/lookup/213.186.33.19.html
JQuery insecurities :
http://retire.insecurity.today/#!/scan/ab25fdce2112f058fa6b1306511d12ccab95203f4fce587e9d241ec1b9b58513
-
Error here as well:
You have 1 error
Wrong certificate installed.
The domain name does not match the certificate common name or SAN.
Warnings
BEAST
The BEAST attack is not mitigated on this server.
This server cannot be scanned for these vulnerabilities:
Poodle (TLS). See possible causes.
SSL Certificate uses a deprecated signature hash
SHA1 certificates expiring in 2017 are no longer trusted in all browsers, and must be replaced with SHA2 certificates immediately to protect against increasingly effective SHA1 attacks
Certificate does not match name neo-net.fr
Subject ssl10.ovh.net
Valid from 05/Mar/2014 to 05/Mar/2017
Issuer AlphaSSL CA - G2
Subject AlphaSSL CA - G2
Valid from 13/Apr/2011 to 13/Apr/2022
Issuer GlobalSign Root CA
Reverse DNS vulnerable to DROWn: https://test.drownattack.com/?site=cluster010.ovh.net
Then there are bad history IP reports on this bad host IP address- some `friendly´ neighbours there:
https://www.virustotal.com/nl/ip-address/213.186.33.19/information/
Last bad host appearance was one month ago: https://www.projecthoneypot.org/ip_213.186.33.19
and https://www.threatminer.org/host.php?q=213.186.33.19
Before you go into denial apart from what has been reported to you earlier in this thread, there is more vulnerability and insecurity than meets the eye at first glance. Website should definitely take up pending issues with OVH the hosting party.
polonus (volunteer website security analyst and website-error hunter)
-
This was indeed a false positive and should be already fixed ;)
-
Although the site is allowed again, the insecurities needs to be fixed.
-
I did some checking out of sheer curiosity and found some things that me wary to visit that website.
For information purposes see http://toolbar.netcraft.com/site_report/?url=neo-net.fr
http://www.nabber.org/projects/dnscheck/?domain=neo-net.fr
http://dnscheck.pingdom.com/?domain=neo-net.fr×tamp=1459527818&view=1
http://www.dnsinspect.com/neo-net.fr/1459527833
https://asafaweb.com/Scan?Url=neo-net.fr
http://www.domxssscanner.com/scan?url=http%3A%2F%2Fneo-net.fr
Tons of errors found here http://push2check.net/neo-net.fr
No blacklists found here http://multirbl.valli.org/lookup/neo-net.fr.html
-
Hi Para-Noid,
There is more than meets the eye at first glance, insecurity that is, also for that PHP version: PHP/5.4.45 - for instance: https://www.exploit-db.com/exploits/38123/
Cookies not flagged as "HttpOnly" may be read by client side script and are at risk of being interpreted by a cross site scripting (XSS) attack. Whilst there are times where a cookie set by the server may be legitimately read by client script, most times the "HttpOnly" flag is missing it is due to oversight rather than by design.
Result
It looks like 3 cookies are being set without the "HttpOnly" flag being set (name : value):
60gpBAK : R122xxx0331
60gp : R41xxx556706
clef_wp_session : cb124478ec065b4df610xxxxxxxxxx0%7C%7C2950605630%7C%7C1459532655
Unless the cookie legitimately needs to be read by JavaScript on the client, the "HttpOnly" flag should always be set to ensure it cannot be read by the client and used in an XSS attack.
WordPress Outdated WordPress Version
4.2.7
Version does not appear to be latest 4.4.2 - update now.
he following plugins were detected by reading the HTML source of the WordPress sites front page.
q2w3-fixed-widget 4.0.6 latest release (4.0.6)
http://www.q2w3.ru/q2w3-fixed-widget-wordpress-plugin/
wpclef 2.1.1 latest release (2.4.1) Update required
http://wordpress.org/extend/plugins/wpclef
download-manager latest release (2.8.93)
http://www.wpdownloadmanager.com/purchases/
contextual-related-posts latest release (2.2.3)
https://webberzone.com/plugins/contextual-related-posts/
cookie-law-info 1.5.3 latest release (1.5.3)
http://wordpress.org/extend/plugins/cookie-law-info/description/
wysija-newsletters 2.6.16 latest release (2.7.1) Update required
http://www.mailpoet.com/
wp-downloadmanager 1.62 latest release (1.67) Update required
http://lesterchan.net/portfolio/programming/php/
Plugins are a source of many security vulnerabilities within WordPress installations, always keep them updated to the latest version available and check the developers plugin page for information about security related updates and fixes.
Warning User Enumeration is possible :o
The first two user ID's were tested to determine if user enumeration is possible.
ID User Login
1 None admin
2 None
It is recommended to rename the admin user account to reduce the chance of brute force attacks occurring. As this will reduce the chance of automated password attackers gaining access. However it is important to understand that if the author archives are enabled it is usually possible to enumerate all users within a WordPress installation.
Warning Directory Indexing Enabled :o
In the test we attempted to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is an information leakage vulnerability that can reveal sensitive information regarding your site configuration or content.
/wp-content/uploads/ enabled
/wp-content/plugins/ disabled
Directory indexing was tested on the /wp-content/uploads/ and /wp-content/plugins/ directores. Note that other directories may have this web server feature enabled, so ensure you check other folders in your installation. It is good practice to ensure directory indexing is disabled for your full WordPress installation either through the web server configuration or .htaccess.
Website owner should also hire someone to configure WordPress CMS correctly and in the first place keep it fully updated (also plug-ins)
polonus (volunteer website security analyst and website error-hunter)