First published: Tue Mar 31 2009(Updated: )
mapserv in MapServer 4.x before 4.10.4 and 5.x before 5.2.2 allows remote attackers to read arbitrary invalid .map files via a full pathname in the map parameter, which triggers the display of partial file contents within an error message, as demonstrated by a /tmp/sekrut.map symlink.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
MapServer | =4.0 | |
MapServer | =4.0-beta1 | |
MapServer | =4.0-beta2 | |
MapServer | =4.2.0-beta1 | |
MapServer | =4.4.0-beta1 | |
MapServer | =4.4.0-beta2 | |
MapServer | =4.6.0-beta1 | |
MapServer | =4.6.0-beta2 | |
MapServer | =4.6.0-beta3 | |
MapServer | =4.8.0-beta2 | |
MapServer | =4.8.0-beta1 | |
MapServer | =4.8.0-beta3 | |
MapServer | =4.8.0-rc2 | |
MapServer | =4.8.0-rc1 | |
MapServer | =4.10.0 | |
MapServer | =4.10.0-beta1 | |
MapServer | =4.10.0-rc1 | |
MapServer | =4.10.0-beta3 | |
MapServer | =4.10.0-beta2 | |
MapServer | =4.10.2 | |
MapServer | =4.10.1 | |
MapServer | =4.10.3 | |
MapServer | =5.0.0-beta5 | |
MapServer | =5.0.0-beta6 | |
MapServer | =5.0.0-beta3 | |
MapServer | =5.0.0-beta4 | |
MapServer | =5.0.0-beta1 | |
MapServer | =5.0.0-beta2 | |
MapServer | =5.0.0-rc1 | |
MapServer | =5.2.0 | |
MapServer | =5.2.0-beta2 | |
MapServer | =5.2.0-beta1 | |
MapServer | =5.2.0-beta3 | |
MapServer | =5.2.0-beta4 | |
MapServer | =5.2.0-rc1 | |
MapServer | =5.2.1 | |
MapServer | =4.6.0 | |
MapServer | =4.6.0-rc1 | |
MapServer | =5.0.0-rc2 | |
MapServer | =5.0.0 | |
MapServer | =4.4.0 | |
MapServer | =4.4.0-beta3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-0842 has been classified with a medium severity rating due to its potential for information disclosure.
To fix CVE-2009-0842, upgrade your MapServer installation to version 4.10.4 or later, or 5.2.2 or later.
CVE-2009-0842 affects MapServer versions 4.x before 4.10.4 and 5.x before 5.2.2.
Yes, CVE-2009-0842 can allow remote attackers to read arbitrary file contents, potentially leading to data breaches.
A workaround for CVE-2009-0842 is to restrict user access to the application and monitor logs for any unauthorized attempts.