Urgent.News

What's breaking now, across thousands of outlets.

Tech

1659 MQTT, 2503 InfluxDB and 45150 ClickHouse Results: The Data Pipeline Layer

1659 MQTT, 2503 InfluxDB and 45150 ClickHouse Results: The Data Pipeline Layer Message brokers and time-series databases sit between the sensors and the dashboards. They are rarely classified as critical infrastructure and they frequently hold the most complete record of what an organisation is doing. A ZoomEye query set collected on 22 September 2026 returned: Query Total results port:8123…

Five data pipeline services, MQTT, InfluxDB, ClickHouse, Cassandra, and Elasticsearch, were queried on September 22, 2026. The results revealed a wide distribution of active ports: ClickHouse exposed 45,150 on HTTP, InfluxDB reported 2,503 on HTTP, MQTT logged 1,659, Cassandra had 15,906, and Elasticsearch logged 1,550. These services are often employed as components of managed platforms, typically residing on public interfaces due to their integral role in observability and analytics stacks.

ClickHouse's vast result count stems from its HTTP interface, which is the most commonly used client library. InfluxDB's HTTP API, while less secured, is the primary administrative interface. MQTT brokers, with a moderate count of 1,659, are unencrypted and often permit anonymous connections, posing a risk for command injection in IoT deployments.

Cassandra and Elasticsearch, while less queried, also present potential security concerns due to their optional authentication and historically unsecured access patterns. The under-management of these services, often attributed to their integration into application stacks and lack of inclusion in security team inventories, underscores the need for proactive checks.

Specifically, scanning netblocks for the listed ports, inspecting listen addresses, auditing authentication states, verifying data classification, and reviewing cloud security group rules are crucial steps in securing these data pipeline layers.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why Schema Diagrams Go Stale (and the Fix)

The short version Schema diagrams go stale because they're static snapshots of a moving target. A migration adds a column, someone renames a table, and suddenly your beautiful diagram is wrong.

  • Schema diagrams are static representations of dynamic databases.
  • Outdated diagrams lead to inaccurate information after migrations.
  • Generate diagrams directly from live database in every deployment.

Building a Geo-fencing Engine: Why I Ditched Google's Geofencing API

Opening hook It happened during a critical board meeting. The room was silent, the kind of silence that amplifies every nervous breath.

  • Speaker's phone disrupted board meeting, highlighting context-aware device issues
  • Custom Geo-fencing engine built using FusedLocationProviderClient for control
  • Importance of understanding Android's power management systems for reliable solutions

More from Tuesday 22 September →