Issued:

2011-03-01

Updated:

2011-03-01

RHSA-2011:0313 - Critical: seamonkey security update

Synopsis

Critical: seamonkey security update

Type/Severity

Security Advisory Critical

Topic

Updated seamonkey packages that fix several security issues are now available for Red Hat Enterprise Linux 4.

The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Description

SeaMonkey is an open source web browser, email and newsgroup client, IRC chat client, and HTML editor.

A flaw was found in the way SeaMonkey handled dialog boxes. An attacker could use this flaw to create a malicious web page that would present a blank dialog box that has non-functioning buttons. If a user closes the dialog box window, it could unexpectedly grant the malicious web page elevated privileges. (CVE-2011-0051)

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause SeaMonkey to crash or, potentially, execute arbitrary code with the privileges of the user running SeaMonkey. (CVE-2011-0053)

A flaw was found in the way SeaMonkey handled plug-ins that perform HTTP requests. If a plug-in performed an HTTP request, and the server sent a 307 redirect response, the plug-in was not notified, and the HTTP request was forwarded. The forwarded request could contain custom headers, which could result in a Cross Site Request Forgery attack. (CVE-2011-0059)

All SeaMonkey users should upgrade to these updated packages, which correct these issues. After installing the update, SeaMonkey must be restarted for the changes to take effect.

Solution

Before applying this update, make sure all previously-released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at This content is not included.http://kbase.redhat.com/faq/docs/DOC-11259

Affected Products

Updated Packages

• seamonkey-js-debugger-1.0.9-67.el4_8.x86_64.rpm
• seamonkey-dom-inspector-1.0.9-67.el4_8.ppc.rpm
• seamonkey-1.0.9-67.el4_8.i386.rpm
• seamonkey-chat-1.0.9-67.el4_8.s390x.rpm
• seamonkey-devel-1.0.9-67.el4_8.s390x.rpm
• seamonkey-mail-1.0.9-67.el4_8.ia64.rpm
• seamonkey-1.0.9-67.el4_8.x86_64.rpm
• seamonkey-dom-inspector-1.0.9-67.el4_8.s390.rpm
• seamonkey-devel-1.0.9-67.el4_8.s390.rpm
• seamonkey-dom-inspector-1.0.9-67.el4_8.ia64.rpm
• seamonkey-dom-inspector-1.0.9-67.el4_8.s390x.rpm
• seamonkey-dom-inspector-1.0.9-67.el4_8.i386.rpm
• seamonkey-js-debugger-1.0.9-67.el4_8.ia64.rpm
• seamonkey-chat-1.0.9-67.el4_8.s390.rpm
• seamonkey-chat-1.0.9-67.el4_8.i386.rpm
• seamonkey-js-debugger-1.0.9-67.el4_8.s390x.rpm
• seamonkey-devel-1.0.9-67.el4_8.i386.rpm
• seamonkey-mail-1.0.9-67.el4_8.s390x.rpm
• seamonkey-mail-1.0.9-67.el4_8.s390.rpm
• seamonkey-mail-1.0.9-67.el4_8.ppc.rpm
• seamonkey-devel-1.0.9-67.el4_8.x86_64.rpm
• seamonkey-js-debugger-1.0.9-67.el4_8.i386.rpm
• seamonkey-chat-1.0.9-67.el4_8.x86_64.rpm
• seamonkey-js-debugger-1.0.9-67.el4_8.s390.rpm
• seamonkey-mail-1.0.9-67.el4_8.i386.rpm
• seamonkey-1.0.9-67.el4_8.s390x.rpm
• seamonkey-1.0.9-67.el4_8.src.rpm
• seamonkey-1.0.9-67.el4_8.ppc.rpm
• seamonkey-chat-1.0.9-67.el4_8.ia64.rpm
• seamonkey-chat-1.0.9-67.el4_8.ppc.rpm
• seamonkey-devel-1.0.9-67.el4_8.ppc.rpm
• seamonkey-js-debugger-1.0.9-67.el4_8.ppc.rpm
• seamonkey-1.0.9-67.el4_8.ia64.rpm
• seamonkey-devel-1.0.9-67.el4_8.ia64.rpm
• seamonkey-mail-1.0.9-67.el4_8.x86_64.rpm
• seamonkey-dom-inspector-1.0.9-67.el4_8.x86_64.rpm
• seamonkey-1.0.9-67.el4_8.s390.rpm

Fixes

• This content is not included.BZ - 675082
• This content is not included.BZ - 675087
• This content is not included.BZ - 681369

CVEs

• CVE-2011-0053
• CVE-2011-0059
• CVE-2011-0051

References

• https://access.redhat.com/security/updates/classification/#critical

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.