routesrv Component Exposes Sensitive Cluster Data: Early Warning
An early warning has been issued regarding the routesrv component, which reportedly exposes sensitive cluster-wide routing and cache infrastructure data over plain HTTP without any authentication. This affects all routesrv API endpoints.
What happened
The routesrv component, used in Kubernetes clusters, appears to expose the full cluster route topology and cache-cluster topology over plain HTTP with zero authentication. This means that any pod within the Kubernetes cluster can potentially access routesrv and retrieve sensitive data related to the cluster's routing and cache infrastructure. The issue is currently under investigation, and it is recommended to implement authentication for routesrv API endpoints and restrict access to authorized pods only to mitigate potential risks. For more detailed information, please consult the primary source at [GHSA-5587-2x54-jj6h](https://github.com/zalando/skipper/security/advisories/GHSA-5587-2x54-jj6h).
Professional software engineers assessing their own exposure should review their Kubernetes cluster configurations to determine if the routesrv component is in use and whether it is properly secured. If routesrv is present, immediate action should be taken to implement the recommended authentication and access restrictions. Further details on the severity and specific versions affected should be obtained from the primary sources.
How 0Day mitigates this
routesrv is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.