InfluxDB - Port 8086
Become VeryLazyTech member! π
Follow us on:
β Twitter @VeryLazyTech.
πΎ Github @VeryLazyTech.
π Medium @VeryLazyTech.
πΊ YouTube @VeryLazyTech.
π© Telegram @VeryLazyTech.
π΅οΈββοΈ My Site @VeryLazyTech.
Visit our shop for e-books and courses. π
Basic info
What is InfluxDB?
InfluxDB is a purpose-built time series database optimized for handling time-stamped data points. Unlike traditional relational databases, InfluxDB is designed specifically for:
High-velocity data ingestion - Millions of data points per second
Time-based queries - Fast aggregations over time ranges
Automatic data retention - Built-in data expiration policies
Efficient storage - Specialized compression for time series data
Real-time analytics - Fast queries for monitoring and alerting
Time Series Database Concepts
Time Series Data Structure:
Key Terminology:
Measurement - Similar to SQL table (e.g., "cpu", "memory", "disk")
Tags - Indexed metadata (hostname, region, environment)
Fields - Actual data values (usage percentages, counts, etc.)
Point - Single data record with measurement, tags, fields, and timestamp
Series - Collection of points with same measurement and tag set
Bucket (v2.x) - Named location for time series data
Organization (v2.x) - Workspace containing users, buckets, and dashboards
Architecture Differences
InfluxDB v1.x vs v2.x:
Common Use Cases
Monitoring & Observability:
System metrics (CPU, memory, disk, network)
Application performance monitoring (APM)
Infrastructure monitoring with Telegraf
Grafana dashboards
IoT & Sensor Data:
Temperature, humidity, pressure sensors
Industrial equipment telemetry
Smart home data collection
Financial & Business:
Stock market tick data
Transaction monitoring
Business metrics and KPIs
DevOps & Cloud:
Container metrics (Docker, Kubernetes)
Cloud resource utilization
CI/CD pipeline metrics
Default Port
Default Port: 8086
Additional Ports:
8088 - RPC service for backup/restore (v1.x)
8089 - UDP service (optional)
Reconnaissance & Enumeration
Port Scanning
Basic Nmap Scan
Sample Output:
Version Detection
Method 1: HTTP Banner (v1.x)
Method 2: Health Endpoint (v2.x)
Method 3: Query Endpoint Version
Method 4: Web Interface (v2.x)
Service Fingerprinting
Check Available Endpoints
Shodan Queries
Find exposed InfluxDB instances:
Authentication Testing
Check Authentication Requirements (v1.x)
Method 1: CLI Connection
Method 2: HTTP API Test
With Authentication:
Check Authentication Requirements (v2.x)
Method 1: Health Endpoint (No Auth Required)
Method 2: API Requests
Default Credentials
Common Default Credentials (v1.x):
Credential Testing Script:
Brute Force Authentication
Using Hydra (v1.x)
Using Medusa
Custom Python Script
Exploitation - InfluxDB v1.x
Unauthenticated Access (No Auth)
List Databases
List Users
List Measurements (Tables)
List Field Keys (Columns)
List Tag Keys
Query Data
Important Note on Quoting:
Data Exfiltration
Dump Entire Database
Export to CSV Format
Search for Sensitive Data
Creating Admin User (If Auth Disabled)
Create Admin User
Grant Admin Privileges to Existing User
Data Manipulation
Write Data (If Auth Disabled)
Delete Data
Authentication Bypass (CVE-2019-20933)
Vulnerability: JWT Token Bypass
Affected Versions: InfluxDB < 1.7.6
Exploitation:
Manual Exploitation:
Exploitation - InfluxDB v2.x
Token-Based Authentication
Understanding v2.x Tokens:
Finding Tokens:
Common locations where tokens might be found:
v2.x Enumeration
Health Check (No Auth Required)
Using Valid Token
Query Data with Flux
v2.x Data Exfiltration
Dump All Buckets
Search for Sensitive Data
CVE-2024-30896: Operator Token Exposure
Vulnerability Overview:
Affected: InfluxDB OSS 2.x through 2.7.11 (pre-patch)
Impact: Authenticated user can retrieve operator token
Severity: Critical (full instance compromise)
Description:
An authenticated user with read access to the authorization resource in the default organization can list and retrieve the instance-wide operator token. With this token, an attacker gains full administrative access.
Detection:
Exploitation:
Automated Exploit:
Post-Exploitation
Persistence
Create Backdoor User (v1.x)
Create Backdoor Token (v2.x)
Data Poisoning
Privilege Escalation
From Read-Only to Admin (v1.x)
Token Privilege Escalation (v2.x)
Lateral Movement
Extract Credentials from Data
Map Infrastructure
Defense & Hardening
Secure Configuration (v1.x)
Enable Authentication
Create Strong Admin Credentials
Remove Default Users
Secure Configuration (v2.x)
Initial Setup with Security
Bind to Localhost
Use TLS/SSL
Token Management Best Practices
Network Security
Firewall Rules
Use Reverse Proxy
Monitoring & Detection
Enable Query Logging
Monitor for Attacks
Intrusion Detection (Snort)
OSSEC/Wazuh Rules
Update & Patch
Check Current Version
Update InfluxDB
Regular Security Audits
Tools & Scripts
Essential Tools
influx - Official CLI client
influxdb-cli - Alternative CLI
curl - HTTP API interaction
jq - JSON parsing
Metasploit - Automated enumeration
nmap - Port scanning
Custom Enumeration Script
Automated Metasploit Module
Cheat Sheet
Quick Reference
Important Endpoints
v1.x:
/ping- Health check, version info/query- Query endpoint/write- Write endpoint/debug/vars- Metrics and stats
v2.x:
/health- Health check, version info/api/v2/query- Flux query endpoint/api/v2/write- Write endpoint/api/v2/organizations- List orgs/api/v2/buckets- List buckets/api/v2/authorizations- List tokens/metrics- Prometheus metrics
Common Databases/Buckets
Conclusion
InfluxDB, while powerful for time series data management, presents significant security risks when misconfigured. From unauthenticated access to critical vulnerabilities like CVE-2019-20933 and CVE-2024-30896, InfluxDB instances require careful security consideration.
Key Takeaways:
Enable authentication on all instances (v1.x and v2.x)
Bind to localhost unless remote access is required
Update immediately to patched versions
Use strong credentials and rotate tokens regularly
Implement network segmentation with firewall rules
Monitor for attacks with proper logging
Audit regularly for misconfigurations
Principle of least privilege for tokens and users
Use TLS/SSL for production deployments
Defense in depth - multiple security layers
Attack Vectors:
Unauthenticated access (misconfiguration)
Default credentials
CVE-2019-20933 (JWT bypass)
CVE-2024-30896 (operator token exposure)
Data exfiltration (sensitive metrics)
Privilege escalation via token manipulation
Remember to only perform these techniques during authorized security assessments. Unauthorized access is illegal and unethical.
Additional Resources
Learn & practice For the Bug Bounty
Last updated