CVE-2026-54354
Description
A flaw was found in MapServer, a system for developing web-based Geographic Information System (GIS) applications. The PostGIS runtime filter translation incorrectly processes attacker-controlled input as numeric without proper validation. This allows an unauthenticated remote attacker, with access to an affected query endpoint, to inject malicious SQL commands. Successful exploitation can lead to bypassing security predicates, accessing unintended database records, and increasing database load.
Statement
Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.
Mitigation
To mitigate this issue, restrict network access to the MapServer instance, especially the affected query endpoint, to trusted clients only. If the PostGIS feature is not required, consider disabling it or reconfiguring MapServer to avoid the vulnerable PostGIS connection and GML metadata settings. Implementing a firewall rule to limit access to the MapServer port can reduce exposure.
Understanding the Weakness (CWE)
Confidentiality,Integrity,Availability
Technical Impact: Execute Unauthorized Code or Commands
Adversaries could execute system commands, typically by changing the SQL statement to redirect output to a file that can then be executed.
Confidentiality
Technical Impact: Read Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
Authentication
Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism
If poor SQL commands are used to check user names and passwords or perform other kinds of authentication, it may be possible to connect to the product as another user with no previous knowledge of the password.
Access Control
Technical Impact: Bypass Protection Mechanism
If authorization information is held in a SQL database, it may be possible to change this information through the successful exploitation of a SQL injection vulnerability.
Integrity
Technical Impact: Modify Application Data
Just as it may be possible to read sensitive information, it is also possible to modify or even delete this information with a SQL injection attack.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
