GeoNetwork: ACL bypass on Elasticsearch search when request body omits query field
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.2.16, 4.4.11
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.2.16, 4.4.11.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- Fix
- Fixed in 4.2.16, 4.4.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
GeoNetwork, a catalog application for managing spatially referenced resources, is affected by a flaw in its Elasticsearch-backed search that can bypass access controls when a search request leaves out the query field. An unauthenticated remote user could use this to view the full indexed contents of metadata records that should be restricted from public access.
Read the original description
GeoNetwork is a catalog application to manage spatially referenced resources. From 4.0.0-alpha.1 until 4.2.16 and 4.4.11, the Elasticsearch-backed search proxy can skip GeoNetwork's access-control filter injection when a client request has an omitted query field. The request is then forwarded to Elasticsearch without group visibility, draft exclusion, record ownership, or portal-specific filtering. An unauthenticated remote attacker can use the affected public search API to retrieve the full indexed contents of metadata records that should not be publicly visible. This issue is fixed in versions 4.2.16 and 4.4.11.
What to do
Upgrade to a fixed version: 4.2.16, 4.4.11.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- geonetwork core-geonetwork
From 4.0.0-alpha.1 · through 4.0.6-0; From 4.2.0 · fixed in 4.2.16; From 4.4.0 · fixed in 4.4.11
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.