Bug 513642 - mapserver: Improper handling of CGI query string fields
Summary: mapserver: Improper handling of CGI query string fields
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://trac.osgeo.org/mapserver/ticke...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-24 15:41 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:31 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-22 18:45:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Lieskovsky 2009-07-24 15:41:27 UTC
An input validation flaw was found in the way mapserver's mapserv CGI form
results decoding script used to handle certain fields of the provided
CGI query string. A remote attacker could use this flaw to write
(potentially malicious) data to certain file system places with the
privileges of the web server user or escalate his privileges by providing
a specially-crafted map file.

References:
-----------
http://trac.osgeo.org/mapserver/ticket/1836
https://bugs.launchpad.net/ubuntu/+source/mapserver/+bug/398814

From the mapserver/ticket/1836:
-------------------------------

"07/22/09 23:42:40 changed by sdlime  
 Back ported to 5.0 and 5.2 branches for completeness...
 Steve"

Proof of Concept:
-----------------
firefox http://biometry.gis.umn.edu/cgi-bin/mapserv.exe?map=/boot/grub/device.map  -> 

 msLoadMap(): Unknown identifier. Parsing error near (hd0):(line 1) 

Tested mapserver version: 
-------------------------
mapserver-5.2.1-6.fc11

Further information:
---------------------
In case this issue was already addressed within

    https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-0842

feel free to close this Bugzilla record.

Comment 1 Josh Bressers 2010-03-22 18:45:07 UTC
mapserver has been updated to >= 5.4, which according to upstream doesn't have this problem.


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