Inbound Connection to an Unsecure Elasticsearch Node
Identifies Elasticsearch nodes that do not have Transport Layer Security (TLS), and/or lack authentication, and are accepting inbound network connections over the default Elasticsearch port.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2020/08/11"
3integration = ["network_traffic"]
4maturity = "production"
5updated_date = "2024/05/21"
6
7[rule]
8author = ["Elastic"]
9description = """
10Identifies Elasticsearch nodes that do not have Transport Layer Security (TLS), and/or lack authentication, and are
11accepting inbound network connections over the default Elasticsearch port.
12"""
13false_positives = [
14 """
15 If you have front-facing proxies that provide authentication and TLS, this rule would need to be tuned to eliminate
16 the source IP address of your reverse-proxy.
17 """,
18]
19from = "now-9m"
20index = ["packetbeat-*", "logs-network_traffic.*"]
21language = "lucene"
22license = "Elastic License v2"
23name = "Inbound Connection to an Unsecure Elasticsearch Node"
24note = """## Setup
25
26This rule requires the addition of port `9200` and `send_all_headers` to the `HTTP` protocol configuration in `packetbeat.yml`. See the References section for additional configuration documentation."""
27references = [
28 "https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-security.html",
29 "https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-http-options.html#_send_all_headers",
30]
31risk_score = 47
32rule_id = "31295df3-277b-4c56-a1fb-84e31b4222a9"
33severity = "medium"
34tags = ["Use Case: Threat Detection", "Tactic: Initial Access", "Domain: Endpoint"]
35timestamp_override = "event.ingested"
36type = "query"
37
38query = '''
39(event.dataset: network_traffic.http OR (event.category: network_traffic AND network.protocol: http)) AND
40 status:OK AND destination.port:9200 AND network.direction:inbound AND NOT http.response.headers.content-type:"image/x-icon" AND NOT
41 _exists_:http.request.headers.authorization
42'''
43
44
45[[rule.threat]]
46framework = "MITRE ATT&CK"
47[[rule.threat.technique]]
48id = "T1190"
49name = "Exploit Public-Facing Application"
50reference = "https://attack.mitre.org/techniques/T1190/"
51
52
53[rule.threat.tactic]
54id = "TA0001"
55name = "Initial Access"
56reference = "https://attack.mitre.org/tactics/TA0001/"
Setup
This rule requires the addition of port 9200
and send_all_headers
to the HTTP
protocol configuration in packetbeat.yml
. See the References section for additional configuration documentation.
References
Related rules
- Execution from a Removable Media with Network Connection
- Potential Buffer Overflow Attack Detected
- Potential Masquerading as Business App Installer
- Potential Remote Code Execution via Web Server
- Potential Remote File Execution via MSIEXEC