Showing posts with label white-hat. Show all posts
Showing posts with label white-hat. Show all posts

Thursday, 11 June 2015

6kbbs v8.0 Weak Encryption Cryptography Security Vulnerabilities




















6kbbs v8.0 Weak Encryption Cryptography Security Vulnerabilities


Exploit Title: 6kbbs Weak Encryption Web Security Vulnerabilities
Vendor: 6kbbs
Product: 6kbbs
Vulnerable Versions: v7.1   v8.0
Tested Version: v7.1   v8.0
Advisory Publication: June 08, 2015
Latest Update: June 10, 2015
Vulnerability Type: Inadequate Encryption Strength [CWE-326]
CVE Reference: *
CVSS Severity (version 2.0):
Discover and Reporter: Wang Jing [School of Physical and Mathematical Sciences (SPMS), Nanyang Technological University (NTU), Singapore] (@justqdjing)





Recommendation Details:


(1) Vendor & Product Description:


Vendor:
6kbbs



Product & Vulnerable Versions:
6kbbs
v7.1
v8.0



Vendor URL & download:
6kbbs can be gain from here,
http://www.6kbbs.com/download.html




Product Introduction Overview:
"6kbbs V8.0 is a PHP + MySQL built using high-performance forum, has the code simple, easy to use, powerful, fast and so on. It is an excellent community forum program. The program is simple but not simple; fast, small; Interface generous and good scalability; functional and practical pursuing superior performance, good interface, the user's preferred utility functions. Forum Technical realization (a) interface : using XHTML + CSS structure, so the structure of the page , easy to modify the interface ; save the transmission static page code , greatly reducing the amount of data transmitted over the network ; improve the interface scalability , more in line with WEB standards, support Internet Explorer, FireFox, Opera and other major browsers. (b) Program : The ASP + ACCESS mature technology , the installation process is extremely simple , the environment is also very common."


"(1) PHP version : (a) 6kbbs V8.0 start using PHP + MySQL architecture. (b) Currently ( July 2010 ) is still in the testing phase , 6kbbs V8.0 is the latest official release. (2) ASP Version: 6kbbs (6k Forum) is an excellent community forum process . The program is simple but not simple ; fast , small ; interface generous and good scalability ; functional and practical . pursue superiority , good interface , practical functions of choice for subscribers."





(2) Vulnerability Details:
6kbbs web application has a computer security problem. It can be exploited by weak encryption attacks. The software stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources.


Several 6kbbs products 0-day web cyber bugs have been found by some other bug hunter researchers before. 6kbbs has patched some of them. "The Full Disclosure mailing list is a public forum for detailed discussion of vulnerabilities and exploitation techniques, as well as tools, papers, news, and events of interest to the community. FD differs from other security lists in its open nature and support for researchers' right to decide how to disclose their own discovered bugs. The full disclosure movement has been credited with forcing vendors to better secure their products and to publicly acknowledge and fix flaws rather than hide them. Vendor legal intimidation and censorship attempts are not tolerated here!" A great many of the web securities have been published here.




Source Code:
<?php
if(empty($row)){
        $extrow=$db->row_select_one("users","username='{$username}'");
        if(!empty($extrow) && !empty($extrow['salt'])){
                if(md5(md5($userpass).$extrow['salt'])==$extrow['userpass']){
                        $row=$extrow; 
                        $new_row["userpass"]=$userpass_encrypt;
                        $new_row["salt"]="";
                        $db->row_update("users",$new_row,"id={$extrow['id']}");
                }
        }
}
?>



Source Code From:
http://code.google.com/p/6kbbs/source/browse/trunk/convert/discuz72/loginext.php?r=16


We can see that "userpass" stored in cookie was encrypted using "$userpass" user password directly. And there is no "HttpOnly" attribute at all. Since md5 is used for the encryption, it is easy for hackers to break the encrypted message.


"The MD5 message-digest cryptography algorithm is a widely used cryptographic hash function producing a 128-bit (16-byte) hash value, typically expressed in text format as a 32 digit hexadecimal number. Papers about it have been published on Eurocrypt, Asiacrypt and Crypto. Meanwhile, researchers focusing on it spread in Computer Science, Computer Engineering, IEEE and Mathematics. MD5 has been utilized in a wide variety of cryptographic applications, and is also commonly used to verify data integrity. MD5 was designed by Ronald Rivest in 1991 to replace an earlier hash function, MD4. The source code in RFC 1321 contains a "by attribution" RSA license." (Wikipedia)







References:
http://tetraph.com/security/weak-encryption/6kbbs-v8-0-weak-encryption/
http://www.inzeed.com/kaleidoscope/computer-security/6kbbs-v8-0-weak-encryption/
https://itswift.wordpress.com/2015/06/11/6kbbs-v8-0-weak-encryption/
http://marc.info/?l=full-disclosure&m=142821698311838&w=4
http://permalink.gmane.org/gmane.comp.security.fulldisclosure/1820
http://seclists.org/fulldisclosure/2015/Apr/13
https://packetstormsecurity.com/files/131290/6kbbs-8.0-Cross-Site-Request-Forgery.html
http://lists.openwall.net/full-disclosure/2015/04/05/6
https://www.mail-archive.com/fulldisclosure%40seclists.org/msg01903.html
http://cxsecurity.com/search/author/DESC/AND/FIND/0/10/Wang+Jing/
http://diebiyi.com/articles/security/6kbbs-v8-0-weak-encryption/
http://whitehatpost.blog.163.com/blog/static/24223205420155115152896/
http://webtechhut.blogspot.com/2015/06/6kbbs-weak-encryption.html
https://webtechwire.wordpress.com/2015/06/11/6kbbs-v8-0-weak-encryption/



Monday, 29 December 2014

Newtelligence DasBlog CVE-2014-7292 Open Redirection Vulnerability

Newtelligence DasBlog CVE-2014-7292 Open Redirection Vulnerability



Bugtraq ID:     70654
Class:     Input Validation Error
CVE:     CVE-2014-7292
Remote:     Yes
Local:     No
Published:     Oct 20 2014 12:00AM
Updated:     Oct 20 2014 12:00AM
Credit:     Wang Jing





http://www.securityfocus.com/bid/70654

Friday, 12 December 2014

Oracle Access Manager CVE-2014-2452 Remote Security Vulnerability

Oracle Access Manager CVE-2014-2452 Remote Security Vulnerability

Bugtraq ID:    66865
Class:    Unknown
CVE:    CVE-2014-2452
Remote:    Yes
Local:    No
Published:    Apr 15 2014 12:00AM
Updated:    Jun 11 2014 12:42PM
Credit:    Jing Wang

Monday, 8 December 2014

Times of India website vulnerable to Cross Site Scripting (XSS) attacks


Times of India website vulnerable to Cross Site Scripting (XSS) attacks




India’s premier daily and popular website, Times of India is vulnerable to critical cross site scripting (XSS) attacks.  Times of India which operates a website called indiatimes.com is a top news website in India and elsewhere.




computer_lightning



The XSS vulnerability in the Times of India website was discovered by Wang Jing, School of Physical and Mathematical Sciences, Nanyang Technological University, Singapore.  He has found that the vulnerability occurs at Indiatimes’s URL links. Indiatimes only party filters the filenames in its website.  Jing says due to this almost all URLs under Indiatimes’s “Photogallery” and “Top-lists” topics are affected by this vulnerability.



Security-Bug: Facebook- und Google-Login unsicher


Security-Bug: Facebook- und Google-Login unsicher



Der nächste Hammer nach dem OpenSSL-Bug: Die sehr weit verbreiteten Login-Protokolle OpenID und OAuth 2.0 haben eine Sicherheitslücke, über die Angreifer an vertrauliche Daten der Nutzer gelangen können. Dies fand Wang Jing, ein Student der Nanyang Technological University in Singapur, heraus. Betroffen sind diverse große Webdienste, die auf diese Protokolle setzen, zum Beispiel Google, Facebook, Microsoft und PayPal.






Sicherheitsrisiko: Login via Facebook oder Google sind angreifbar


OpenID und OAuth, wie OpenSSL Open-Source-Anwendungen, dienen als Login-Methode für Webdienste und Apps. User können sich darüber mit einem bestehenden Konto (etwa von Facebook oder Google) bei dem Dienst registrieren, ohne dort ein eigenes Benutzerkonto anlegen zu müssen. Ähnlich funktioniert auch die Anmeldung bei Facebook-Apps. In beiden Fällen hat der User den Vorteil, dass seine Anmeldedaten bei Google oder Facebook bleiben, der neue Dienst also weder E-Mail-Adresse noch Passwort erhält.


http://www.chip.de/news/Security-Bug-Facebook-und-Google-Login-unsicher_69512331.html