Language Selection

English French German Italian Portuguese Spanish

Mozilla Updates Firefox to Fix Security Gaps

Filed under
Moz/FF

The Mozilla Foundation updated the Firefox Web browser Tuesday in order to patch a series of security vulnerabilities, including widely publicized browser spoofing issue and a frame-injection issue.

Mozilla has released Firefox 1.0.5 and plans to follow it with new versions of its Thunderbird e-mail client and namesake browser application suite on Wednesday, said Chris Hofmann, Mozilla's director of engineering.

The Firefox update fixes 11 security issues discovered both by outside security researchers and from Mozilla's own Security Bug Bounty Program, which offers a $500 reward for reporting bugs.

Hofmann said that Mozilla knows of no exploits of the security vulnerabilities patched in Firefox 1.0.5.

Among the vulnerabilities plugged in Firefox 1.0.5 is a browser spoofing issue reported last month by security researcher Secunia. The spoofing vulnerability, which affected all major browsers, could aid scammers in successfully launching phishing attacks.

Users could be convinced to provide sensitive information in JavaScript dialog boxes that do not display their origins. To fix the issue, the Firefox upgrade now displays in a JavaScript window's header the Web address of the source of the prompt's content, Hofmann said.

Also last month, a 7-year-old frame-injection vulnerability, which had been patched in earlier versions of Mozilla browsers, reared its head again in Firefox.

The new version patches the flaw, which had the potential to allow an attacker to load malicious content in the browser window of a trusted Web site by exploiting the way browsers handle frames.

It is working on a revamped software updating system for the next major release of Firefox, Version 1.1, which is due for release later this summer.

A second alpha release of Firefox 1.1, called "Deer Park," was slated to be available for testing among developers as soon as Tuesday.

That alpha was supposed to include early test code of the new software updates system, Hofmann said.

Full Story.

Strange

I went to the mozilla site to get the source for 1.0.5 to rebuild my rpm for pclos and there source isnt listed as yet. I guess I'll have to wait until the source shows up in their repo.

re: strange

Yeah, dang, it still ain't up.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Development News: Rust 1.17 and SourceForge

  • Announcing Rust 1.17
    The Rust team is happy to announce the latest version of Rust, 1.17.0. Rust is a systems programming language focused on safety, speed, and concurrency.
  • Rust 1.17 Released
    Judging by the massive Rust fan base in our forums, those of you reading this will be delighted today about the newest version of Rustlang, v1.17.
  • SourceForge: Let's hold hands in a post-CodePlex world [Ed: Microsoft Gavin needlessly interjects Microsoft into it. Like CodePlex was EVER relevant…]
    President Logan Abbott has said he’ll seek tighter integration between SourceForge’s tools and those of others – including giant rival GitHub.

Nouveau Re-Clocked With DRM-Next Linux 4.12 + Mesa 17.2-dev vs. NVIDIA 381 Driver

A few days back I posted benchmarks of the initial GTX 1050/1060/1070/1080 Nouveau 3D support. As expected, the performance was rather abysmal with re-clocking not being available for Pascal (or Maxwell) GPUs on this open-source NVIDIA Linux kernel driver. For those trying to use Nouveau for Linux games or care about your GPU clock speeds, currently the GTX 600/700 "Kepler" series is still your best bet or the GTX 750 "Maxwell 1" is the last NVIDIA graphics processors not requiring signed firmware images and can properly -- but manually -- re-clock with the current Nouveau driver. Read more

Coverage From Recent Linux Conferences

Supply Chain Case Study: Canonical and Ubuntu

I love talking about supply chain management in an open source software context, especially as it applies to managing collaborative processes between upstream projects and their downstream products. In the article linked above, I called out a couple of examples of supply chain management: an enterprise OpenStack distribution and a container management product utilizing Kubernetes and Docker for upstream platforms. What about anti-patterns or things to avoid? There are several we could call out. At the risk of picking on someone I like, I’ll choose Canonical simply because they’ve been in the headlines recently for changes they’ve made to their organization, cutting back on some efforts and laying off some people. As I look at Canonical from a product offering perspective, there’s a lot they got right, which others could benefit from. But they also made many mistakes, some of which could have been avoided. First, the good. Read more