Database crash with invalid geoJSON input
Bug #1438875 reported by
Johan Van de Wauw
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgis (Debian) |
Fix Released
|
Unknown
|
|||
postgis (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Utopic |
Fix Released
|
Undecided
|
Unassigned | ||
Vivid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As reported upstream:
http://
Malformed geoJSON data can kill the database process. This functionality exists in trusty, utopic and vivid.
A fix has been prepared in debian unstable - an unblock request for jessie was requested:
https:/
Changed in postgis (Debian): | |
status: | Unknown → Confirmed |
Changed in postgis (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
information type: | Private Security → Public Security |
Changed in postgis (Debian): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Since the debian bug and the upstream bug report are public, there's no point in keeping this bug report private, so I've made it public as well. Has a CVE been assigned for this issue?