Bug 182579 - CVE-2006-0188 Possible XSS through right_frame parameter in webmail.php
CVE-2006-0188 Possible XSS through right_frame parameter in webmail.php
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: squirrelmail (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
source=secunia,reported=20060222,publ...
: Security
Depends On:
Blocks: 170416
  Show dependency treegraph
 
Reported: 2006-02-23 09:55 EST by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2006-0283
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-03 12:26:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2006-02-23 09:55:16 EST
Possible XSS through right_frame parameter in webmail.php
http://www.squirrelmail.org/security/issue/2006-02-01

(Text taken from the above URL)
The right_frame parameter in webmail.php was not properly sanitized,
and could allow for an attacker to replace the right frame of a
tricked user with content from another host within the SquirrelMail
interface.  Some of the attack vectors are only possible with Internet
Explorer.

source=secunia,reported=20060222,public=20060201
Comment 2 Josh Bressers 2006-03-02 16:11:20 EST
This issue also affects RHEL3
Comment 3 Tim Burke 2006-03-10 11:41:14 EST
Adding to U4 proposed list.
Comment 6 Red Hat Bugzilla 2006-05-03 12:26:39 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0283.html

Note You need to log in before you can comment on or make changes to this bug.