Elasticsearch identification via exposed search headers
Published Feb 11, 2025 · Updated Feb 12, 2025
Information disclosure in GeoNetwork opensource before 4.2.10 and 4.4.0 through 4.4.4 allows remote attackers to identify Elasticsearch. The search service returns Elasticsearch-identifying response headers from POST requests to its records search endpoints instead of suppressing them. No authentication or user interaction is required; the disclosed software identity supports technology fingerprinting but does not expose catalog data.
Summary
What happened
Information disclosure in GeoNetwork opensource before 4.2.10 and 4.4.0 through 4.4.4 allows remote attackers to identify Elasticsearch. The search service returns Elasticsearch-identifying response headers from POST requests to its records search endpoints instead of suppressing them. No authentication or user interaction is required; the disclosed software identity supports technology fingerprinting but does not expose catalog data.
The record
- CVE
- CVE-2024-32037
- Published
- Feb 11, 2025
- Updated
- Feb 12, 2025
- Vendor
- GeoNetwork
- Product
- GeoNetwork opensource
- Classifications
- CWE-200, T1592.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.2.10
- Affected versionversion=>= 4.4.0, < 4.4.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo