CyberRota Analysis
AI-GeneratedA vulnerability exists in hawtio-operator where, under debug log level 1 or higher, the entire Route object—including sensitive TLS private keys in PEM format—is logged to standard output. This exposure can lead to unauthorized access to sensitive data if logs are forwarded to centralized systems, making them accessible to users with pod/log access in the openshift-operators namespace. Organizations using hawtio-operator should prioritize addressing this issue, especially those that enable debug logging during troubleshooting.
Original NVD Description
A flaw was found in hawtio-operator. When a custom Route TLS secret is configured and the operator runs at debug log level 1 or higher, the entire Route object — including the TLS private key in PEM format — is serialized to JSON and written to the operator's standard output. Operator logs are typically forwarded to centralized logging systems and readable by anyone with pods/log access in the openshift-operators namespace. Debug level 1 is a low threshold commonly enabled during troubleshooting.