Elasticsearch / OpenSearch open to the internet
Elasticsearch and OpenSearch serve a REST API on 9200. Without authentication and with the port exposed, anyone can read, modify or delete every index over HTTP.
Why it matters
Unauthenticated search clusters have leaked billions of records; they're continuously scanned and indexed by services like Shodan.
Ransom notes are often left in an empty index after an exposed cluster is wiped — the data is taken first.
How to check for it
- From outside, curl http://<ip>:9200/_cat/indices — a response without credentials means it's open.
- Confirm security (auth/TLS) is enabled and 9200/9300 aren't reachable from the internet.
How to fix it
- Enable the security features (authentication and TLS), bind to a private interface, and close 9200/9300 at the firewall.
- Put the cluster behind your application network; never expose it directly.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Does enabling security cost anything?
- No — the core security features (auth, TLS, role-based access) are free in current Elasticsearch and in OpenSearch.