First published: Tue Mar 31 2009(Updated: )
The msLoadQuery function in mapserv in MapServer 4.x before 4.10.4 and 5.x before 5.2.2 allows remote attackers to determine the existence of arbitrary files via a full pathname in the queryfile parameter, which triggers different error messages depending on whether this pathname exists.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
MapServer | =4.2.0-beta1 | |
MapServer | =4.4.0 | |
MapServer | =4.4.0-beta1 | |
MapServer | =4.4.0-beta2 | |
MapServer | =4.4.0-beta3 | |
MapServer | =4.6.0 | |
MapServer | =4.6.0-beta1 | |
MapServer | =4.6.0-beta2 | |
MapServer | =4.6.0-beta3 | |
MapServer | =4.6.0-rc1 | |
MapServer | =4.8.0-beta1 | |
MapServer | =4.8.0-beta2 | |
MapServer | =4.8.0-beta3 | |
MapServer | =4.8.0-rc1 | |
MapServer | =4.8.0-rc2 | |
MapServer | =4.10.0 | |
MapServer | =4.10.0-beta1 | |
MapServer | =4.10.0-beta2 | |
MapServer | =4.10.0-beta3 | |
MapServer | =4.10.0-rc1 | |
MapServer | =4.10.1 | |
MapServer | =4.10.2 | |
MapServer | =4.10.3 | |
MapServer | =5.0.0 | |
MapServer | =5.0.0-beta1 | |
MapServer | =5.0.0-beta2 | |
MapServer | =5.0.0-beta3 | |
MapServer | =5.0.0-beta4 | |
MapServer | =5.0.0-beta5 | |
MapServer | =5.0.0-beta6 | |
MapServer | =5.0.0-rc1 | |
MapServer | =5.0.0-rc2 | |
MapServer | =5.2.0 | |
MapServer | =5.2.0-beta1 | |
MapServer | =5.2.0-beta2 | |
MapServer | =5.2.0-beta3 | |
MapServer | =5.2.0-beta4 | |
MapServer | =5.2.0-rc1 | |
MapServer | =5.2.1 | |
MapServer | =4.0 | |
MapServer | =4.0-beta1 | |
MapServer | =4.0-beta2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-0843 is classified as a moderate severity vulnerability due to the information disclosure it can cause.
To fix CVE-2009-0843, upgrade to MapServer version 4.10.4 or higher, or 5.2.2 or higher.
CVE-2009-0843 is caused by the msLoadQuery function allowing remote attackers to ascertain the existence of files via error messages.
CVE-2009-0843 affects MapServer versions 4.x before 4.10.4 and 5.x before 5.2.2.
No, CVE-2009-0843 is not considered critical; it primarily poses a risk of information disclosure.