Hawtio-operator: hawtio-operator: tls private key written to operator log at debug level
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Red Hat | Red Hat build of Apache Camel - HawtIO 4 | affected | — |
No data.
No data.
No data available yet.
Vendor Workaround
Exclude logging sensitive info or apply masking. Set the operator log verbosity to 0 (the default) to prevent TLS key material from being written to logs. If debug logging has been enabled previously, rotate any TLS secrets that may have been exposed in the logs and purge the affected log entries from centralized logging systems.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.194% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Hawtio-operator: hawtio-operator: tls private key written to operator log at debug level | |
| First Time appeared |
Redhat
Redhat apache Camel Hawtio |
|
| Weaknesses | CWE-532 | |
| CPEs | cpe:/a:redhat:apache_camel_hawtio:4 | |
| Vendors & Products |
Redhat
Redhat apache Camel Hawtio |
|
| References |
| |
| Metrics |
cvssV3_1
|