dbcve.org
GeonetworkApplication · Osgeo

CVE-2024-32037

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 4.2.10 / 4.4.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
GeoNetwork is a catalog application to manage spatially referenced resources. In versions prior to 4.2.10 and 4.4.5, the search end-point response headers contain information about Elasticsearch software in use. This information is valuable from a security point of view because it allows software used by the server to be easily identified. GeoNetwork 4.4.5 and 4.2.10 fix this issue. No known workarounds are available.

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 confidence

GeoNetwork versions before 4.2.10 and 4.4.5 expose Elasticsearch version information in HTTP response headers from the search endpoint. This information disclosure allows attackers to fingerprint the exact Elasticsearch software version in use, aiding in targeted exploit development.

MitigationUpgrade GeoNetwork to version 4.2.10 or 4.4.5 (or later) to remove the version disclosure from response headers. No configuration-based workarounds exist.

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
GeonetworkApplication
Affected:< 4.2.10>= 4.4.0, < 4.4.5

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GeoNetwork version
    Access the GeoNetwork admin interface and locate the version information, typically found in the 'About' or 'System Information' section. Alternatively, check any version file or startup logs for the running GeoNetwork version number.
    Affected if The installed version is below 4.2.10 or is 4.4.0 through 4.4.4
  2. Locate the search API endpoint
    Identify the base URL for your GeoNetwork instance. The search functionality is typically accessible at a path such as /geonetwork/srv/api/search or similar search-related endpoints.
    Affected if The endpoint exists and is reachable on the network
  3. Send a request to the search endpoint and inspect response headers
    Use a tool such as curl or a browser's developer tools to send an HTTP request (GET) to the search endpoint. Examine all response headers for any header that reveals the Elasticsearch version, such as 'X-Elastic-Product' or similar headers containing version strings like 'Elasticsearch/7.x.x' or 'Elasticsearch/8.x.x'.
    Affected if The response headers contain an Elasticsearch version identifier (such as a header value showing Elasticsearch and a version number)
  4. Compare your version to the affected ranges
    If Elasticsearch version information was found in the headers, confirm that your GeoNetwork version falls within the affected ranges: version 4.4.0 through 4.4.4, or any version before 4.2.10.
    Affected if Your GeoNetwork version is within the affected ranges AND Elasticsearch version information is exposed in the response headers

You are affected if your GeoNetwork version is below 4.2.10 or between 4.4.0 and 4.4.4 AND the search endpoint response headers contain Elasticsearch version information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.2.10 / 4.4.5 or later
Fixed in 4.2.104.4.5
Interim mitigation

Upgrade GeoNetwork to version 4.2.10 or 4.4.5 (or later) to remove the version disclosure from response headers. No configuration-based workarounds exist.

Recommended fix High confidence

GeoNetwork 4.2.10 (for 4.2.x branch) or GeoNetwork 4.4.5 (for 4.4.x branch)

  1. Identify your current GeoNetwork version using the admin console or system information
  2. Determine which branch you are on (4.2.x or 4.4.x)
  3. For 4.2.x users: Upgrade to GeoNetwork version 4.2.10
  4. For 4.4.x users: Upgrade to GeoNetwork version 4.4.5
  5. After upgrade, verify the search endpoint response headers no longer contain Elasticsearch version information
  6. Test that catalog search functionality continues to work correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geonetwork Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32037 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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