This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 85689 - Squirrelmail xss patch from latetst errrata causes parse error
Squirrelmail xss patch from latetst errrata causes parse error
Status: CLOSED DUPLICATE of bug 82600
Product: Red Hat Linux
Classification: Retired
Component: squirrelmail (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Gary Benson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-05 19:22 EST by Darrin Yeager
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-20 21:53:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Darrin Yeager 2003-03-05 19:22:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Description of problem:
Line 308 of the xss-patch has a parse error after being applied. The offending
line of the patch is:

+    $filename = 'untitled' . strip_tags($passed_ent_id) .$suffix);

which obviously won't parse by php.

Change line in patch to:

+    $filename = 'untitled' . strip_tags($passed_ent_id) . $suffix;

rebuild RPM and re-install.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install new squirrel mail RPM
2. Try to download an attachemnt
3. Parse error in download.php - this was caused by the xss patch.
    

Additional info:
Comment 1 Darrin Yeager 2003-03-05 19:37:13 EST
Found Bug 82600 that appears to be the same as this one. It says it was fixed in
 1.2.10-4, yet errata release (RHSA-2003:042-07) has 1.2.10-1. 
Comment 2 Gary Benson 2003-03-06 04:54:24 EST
1.2.10-4 is in Rawhide.

*** This bug has been marked as a duplicate of 82600 ***

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