Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Mozilla Firefox Memory Corruption and Security Bypass Vulnerabilities
Multiple vulnerabilities have been identified in Mozilla Firefox, which could be exploited by attackers to bypass security restrictions, gain knowledge of sensitive information, cause a denial of service or compromise a vulnerable system.
This thread serves as a discussion place for any current security vulnerabilities in Mozilla Firefox. LQ members are encouraged to subscribe to this thread in order to stay informed about the latest Mozilla Firefox security fixes and workarounds. If this is your first time stopping by this thread, get the latest info by jumping to the last page.
Juan Pablo Lopez Yacubian has discovered a security issue in Mozilla Firefox, which can be exploited by malicious people to display a fake URL in the address bar.
The security issue is caused due to an error when opening a new window for a malformed domain. This can be exploited to display an arbitrary URL in the address bar of a child window by issuing a "window.open()" call with a domain containing e.g. "%20" characters.
The security issue is confirmed in version 3.0.12 and 3.5.1. Other versions may also be affected.
IOActive security researcher Dan Kaminsky reported a mismatch in the treatment of domain names in SSL certificates between SSL clients and the Certificate Authorities (CA) which issue server certificates. In particular, if a malicious person requested a certificate for a host name with an invalid null character in it most CAs would issue the certificate if the requester owned the domain specified after the null, while most SSL clients (browsers) ignored that part of the name and used the unvalidated part in front of the null. This made it possible for attackers to obtain certificates that would function for any site they wished to target. These certificates could be used to intercept and potentially alter encrypted communication between the client and a server such as sensitive bank account transactions.
Moxie Marlinspike reported a heap overflow vulnerability in the code that handles regular expressions in certificate names. This vulnerability could be used to compromise the browser and run arbitrary code by presenting a specially crafted certificate to the client. This code provided compatibility with the non-standard regular expression syntax historically supported by Netscape clients and servers. With version 3.5 Firefox switched to the more limited industry-standard wildcard syntax instead and is not vulnerable to this flaw.