Possible SQL Injections with postgis TIME filters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mapserver (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Unassigned | ||
Quantal |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
See:
As part of @rouault 's WFS 2.0 work he discovered a SQL injection issue specific to WMS-Time and perhaps SOS services. It has to do with PostGIS and time validation. Based on Even's tests for WMS-Time the vulnerability is limited to unintended disclosure of data from the specific table, if specific conditions are met:
WMS-Time is configured
PostGIS is used
GetFeatureInfo output formats dump all attributes (e.g. gmlitems all)
Basically you can muck with the where clause but can’t execute secondary commands (e.g. delete …). It may be possible to access unintended data through the map itself (e.g. via a label item) but that seems pretty hard. Again, SOS services have not been examined.
https:/
Fixes have been issued at: http://
Changed in mapserver (Ubuntu): | |
status: | Incomplete → Confirmed |
information type: | Private Security → Public Security |
Changed in mapserver (Ubuntu Trusty): | |
status: | Confirmed → Fix Released |
Changed in mapserver (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in mapserver (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in mapserver (Ubuntu Raring): | |
status: | New → Confirmed |
Changed in mapserver (Ubuntu Saucy): | |
status: | New → Confirmed |
Changed in mapserver (Ubuntu Precise): | |
importance: | Undecided → Medium |
Changed in mapserver (Ubuntu Quantal): | |
importance: | Undecided → Medium |
Changed in mapserver (Ubuntu Raring): | |
importance: | Undecided → Medium |
Changed in mapserver (Ubuntu Saucy): | |
importance: | Undecided → Medium |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https:/ /wiki.ubuntu. com/SecurityTea m/UpdateProcedu res