Opened 13 years ago
Closed 13 years ago
#3676 closed defect (worksforme)
Specifying an invalid value for BBOX parameter causes mapserver crash
| Reported by: | bleukert | Owned by: | assefa |
|---|---|---|---|
| Priority: | high | Milestone: | 5.6.6 release |
| Component: | WMS Server | Version: | 5.6 |
| Severity: | critical | Keywords: | |
| Cc: | sdlime, dmorissette |
Description
If you specify an invalid value for BBOX parameter in a WMS GetMapRequest the Mapserver CGI process allocates a lot of memory (as much as available on the server) and crashes.
Valid BBOX:
... SRS=EPSG:31466&BBOX=2332859.6391752576,5556390,2896310.3608247424,5845350 ...
Invalid BBOX:
... SRS=EPSG:31466&BBOX=5556390,2896310.3608247424,5845350 ...
Change History (7)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Component: | MapServer CGI → WMS Server |
|---|---|
| Owner: | changed from to |
This is a WMS specific problem I think. The main CGI form processor checks for the correct number and type of extent values and seems to behave just fine in this case.
Changing components...
Steve
comment:3 by , 13 years ago
| Cc: | added |
|---|
comment:4 by , 13 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
comment:5 by , 13 years ago
| Owner: | changed from to |
|---|
Qucikly checking this, I was not able to reproduce.
What does 'invalid' means in this case?
For the wms module invalid would be things like minx>maxx or miny>maxy. In that case an exception is returned immediately.
Is it possible that the 'invalid' the bbox given end up retrieving a large amount of data?
comment:6 by , 13 years ago
Can you also check what were the width/height values in your wms request?
comment:7 by , 13 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Please reopen with test case if this is still an issue.
It seems that this problem only occurs if the EXCEPTIONS parameter is set to application/vnd.ogc.se_inimage or application/vnd.ogc.se_blank.