FedoraOperating system · Fedoraproject
CVE-2021-32062
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMapServer before 7.0.8, 7.1.x and 7.2.x before 7.2.3, 7.3.x and 7.4.x before 7.4.5, and 7.5.x and 7.6.x before 7.6.3 does not properly enforce the MS_MAP_NO_PATH and MS_MAP_PATTERN restrictions that are intended to control the locations from which a mapfile may be loaded (with MapServer CGI).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMapServer CGI fails to properly enforce MS_MAP_NO_PATH and MS_MAP_PATTERN security restrictions that are meant to control which directories mapfiles can be loaded from, potentially allowing attackers to load mapfiles from unauthorized locations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 33= 34< 7.0.8>= 7.1.0, < 7.2.3>= 7.3.0, < 7.4.5>= 7.5.0, < 7.6.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check MapServer versionRun `mapserv -v` or request the CGI binary with `QUERY_STRING=version` to retrieve the installed version numberAffected if The version is less than 7.0.8, or between 7.1.0-7.2.2, 7.3.0-7.4.4, or 7.5.0-7.6.2 (for OSGeo builds); or the system is Fedora 33 or 34 with MapServer included
-
Verify CGI binary is in useConfirm the mapserv CGI binary is being used (not FastCGI or other interface) by checking the web server configuration or observing the binary name in useAffected if The MapServer CGI binary is actively handling mapfile requests
-
Check MS_MAP_NO_PATH settingInspect the CGI environment (environment variables), Apache/Nginx config files, or mapserver.conf for the MS_MAP_NO_PATH parameter. Look for `MS_MAP_NO_PATH` set to a non-zero value (typically 1)Affected if MS_MAP_NO_PATH is not set or is set to 0, meaning path restrictions are not enforced
-
Check MS_MAP_PATTERN settingReview the CGI environment, web server config, or mapserver.conf for MS_MAP_PATTERN. This should be set to a regular expression that restricts which directories mapfiles can be loaded fromAffected if MS_MAP_PATTERN is not configured or is set too permissively (e.g., allows arbitrary paths)
-
Identify loaded mapfile locationsReview mapfile references in web server configuration or application logs to determine which directories mapfiles are being loaded fromAffected if Mapfiles are being loaded from directories outside the intended secure whitelist
You are affected if your MapServer version falls within the vulnerable ranges AND the CGI is in use AND MS_MAP_NO_PATH is not set to 1 or MS_MAP_PATTERN is not properly configured to restrict mapfile loading paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.0.87.2.37.4.5
Upgrade to MapServer 7.0.8, 7.2.3, 7.4.5, or 7.6.3 (or later) to receive the patch, or ensure MS_MAP_NO_PATH and MS_MAP_PATTERN are properly configured to restrict mapfile loading to expected directories.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-32062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data