{"id":57873,"date":"2024-12-15T23:58:08","date_gmt":"2024-12-15T23:58:08","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/are-your-prometheus-servers-and-exporters-secure-probably-not\/"},"modified":"2024-12-15T23:58:08","modified_gmt":"2024-12-15T23:58:08","slug":"are-your-prometheus-servers-and-exporters-secure-probably-not","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/are-your-prometheus-servers-and-exporters-secure-probably-not\/","title":{"rendered":"Are your Prometheus servers and exporters secure? Probably not"},"content":{"rendered":"

Infosec in brief<\/span> There’s a problem of titanic proportions brewing for users of the Prometheus open source monitoring toolkit: hundreds of thousands of servers and exporters are exposed to the internet, creating significant security risks and leaving organizations vulnerable to attack.<\/p>\n

Aqua Security last week reported<\/a> that it discovered more than 296,000 internet-facing Prometheus exporters (tools that export info from other infosec tools into Prometheus) and 40,000 servers were exposed to potential risks.<\/p>\n

Unfortunately, this isn’t so much a problem with Prometheus itself, as the tool’s documentation “presume[s] that untrusted users can view information about Prometheus, specifically the Prometheus HTTP endpoint, logs and debugging information” if proper steps aren’t taken to protect the instances from the wider internet, Aqua explained.<\/p>\n