AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Filezilla keeps disconnecting1/18/2024 ![]() ![]() ![]() – Mozilla: “Disable Flash, it has so many security flaws!” Browse free.Ģ24 comments on “Firefox exploit found in the wild” People who use ad-blocking software may have been protected from this exploit depending on the software and specific filters being used. If you use Firefox on Windows or Linux it would be prudent to change any passwords and keys found in the above-mentioned files if you use the associated programs. The exploit leaves no trace it has been run on the local machine. Mac users are not targeted by this particular exploit but would not be immune should someone create a different payload. ![]() ssh configuration files and keys, configuration files for remina, Filezilla, and Psi+, text files with “pass” and “access” in the names, and any shell scripts. On Linux the exploit goes after the usual global configuration files like /etc/passwd, and then in all the user directories it can access it looks for. purple and Psi+ account information, and site configuration files from eight different popular FTP clients. On Windows the exploit looked for subversion, s3browser, and Filezilla configurations files. ![]() The files it was looking for were surprisingly developer focused for an exploit launched on a general audience news site, though of course we don’t know where else the malicious ad might have been deployed. This allowed it to search for and upload potentially sensitive local files. The vulnerability does not enable the execution of arbitrary code but the exploit was able to inject a JavaScript payload into the local file context. Mozilla products that don’t contain the PDF Viewer, such as Firefox for Android, are not vulnerable. The vulnerability comes from the interaction of the mechanism that enforces JavaScript context separation (the “same origin policy”) and Firefox’s PDF Viewer. The fix has also been shipped in Firefox ESR 38.1.1. All Firefox users are urged to update to Firefox 39.0.3. This morning Mozilla released security updates that fix the vulnerability. We have 80 RW sites and publishing has only ever been an issue once - temporarily after upgrade to RW6.Yesterday morning, August 5, a Firefox user informed us that an advertisement on a news site in Russia was serving a Firefox exploit that searched for sensitive files and uploaded them to a server that appears to be in Ukraine. Then ensure you are publishing ONLY to with the path being public_html - don’t publish other URLs to subfolders they should each have their own account.ĭespite some glitches, RW publishing is pretty rock solid. In your shoes, I would spend a day tidying up your entire folder structure, give every URL a proper name (not just the default RW 'page 11, " etc). Honestly and not meaning to rude, it is quite a mess and I would have to suspect that there may be duplicate page names or something like this going on which is playing havoc with the publishing engine. If you do a site: search for the standard URL, around 320 pages are shown including duplicate page names and some with 2 page numbers To elaborate If you do a site: search for the long URL, 5 pages come up - all duplicates (albeit possibly updated) of pages found on the regular URL but in a different place. Yet you have this URL indexed along with over 300 pages from the URL - none of which have any proper file / folder names. Aside from the publishing issues, why such a convoluted web address? is not normal protocol for a business address. ![]()
0 Comments
Read More
Leave a Reply. |