CVE-2026-77324 in MapServer
Summary
by MITRE • 11/20/2026
MapServer is a system for developing web-based GIS applications. From 4.4.0 until 8.6.5, an unauthenticated remote attacker can send a WCS GetCoverage XML POST request whose BoundingBox element omits the crs attribute, causing xmlGetProp() in src/mapwcs.cpp to return null. msWCSParseRequest() then calls string functions on the null value before normal WCS exception handling, crashing the CGI or FastCGI worker. The analogous KVP or GET path is not affected because it obtains a count-validated, non-null token. A single request can terminate one worker, and repeated requests can exhaust a fixed worker pool and deny service. This issue is fixed in version 8.6.5.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/20/2026
MapServer serves as a foundational system for developing web-based Geographic Information System applications, facilitating the delivery of geospatial data over networks through various protocols including Web Coverage Service. Within versions ranging from 4.4.0 to 8.6.5, a critical vulnerability exists in the handling of WCS GetCoverage requests that allows an unauthenticated remote attacker to trigger a denial of service condition. The flaw resides specifically within the XML parsing logic found in the src/mapwcs.cpp source file. When a client submits a POST request containing a BoundingBox element without the required crs attribute, the internal function xmlGetProp() fails to locate the missing property and consequently returns a null pointer instead of a valid string reference.
The technical severity of this flaw is amplified by how the subsequent processing logic handles this unexpected null value. The msWCSParseRequest() function proceeds to invoke standard C language string manipulation functions on the null pointer returned by xmlGetProp(). This operation constitutes an invalid memory access, leading directly to a segmentation fault or similar critical error that terminates the CGI or FastCGI worker process responsible for handling the request. Unlike this XML-based path, the analogous Key-Value Pair and GET request paths are not susceptible to this specific failure mode because they utilize different parsing mechanisms that include count validation checks, ensuring that tokens retrieved from requests are non-null before being processed further.
The operational impact of this vulnerability is significant due to its potential for causing service disruption with minimal effort from an attacker. A single crafted HTTP POST request containing the malformed BoundingBox element is sufficient to crash one worker process in a typical deployment environment. In scenarios where MapServer operates behind a reverse proxy or load balancer using a fixed pool of workers, repeated exploitation can exhaust all available worker threads. This resource exhaustion results in a complete denial of service for legitimate users attempting to access geospatial data services, effectively rendering the application unavailable without requiring any form of authentication.
From a classification perspective, this vulnerability aligns with CWE-476, which describes a NULL Pointer Dereference error that occurs when software attempts to use an object reference or pointer whose value is null. This type of flaw often leads to crashes and can sometimes be leveraged for more severe outcomes depending on the execution context, although in this specific instance within MapServer's CGI/FastCGI architecture, the primary impact remains denial of service through process termination. The attack vector corresponds to ATT&CK technique T1498.002, representing Network Denial of Service via resource exhaustion using a single or limited number of requests that exploit application logic flaws rather than overwhelming bandwidth capacity.
Mitigation strategies for this vulnerability primarily involve upgrading the MapServer installation to version 8.6.5 or later, where the developers have addressed the null pointer dereference by implementing proper validation and error handling before string operations are performed on data retrieved from XML properties. For organizations unable to immediately patch their systems due to compatibility constraints, temporary mitigations may include deploying a Web Application Firewall configured to inspect incoming WCS POST requests for missing crs attributes in BoundingBox elements and blocking such malformed payloads before they reach the MapServer application layer. Additionally, configuring reverse proxies with strict request validation rules can provide an additional layer of defense against this specific exploitation pattern until permanent remediation is applied.