Authorization header and full chat payloads logged at hard-coded DEBUG default
Summary
A flaw was found in the vllm-orchestrator-gateway component. The system's production binary logs all incoming authorization headers and full chat payloads, which may contain personally identifiable information (PII) and secrets, to persistent logs. This sensitive data, including bearer tokens and chat content, can be accessed by any user with logging privileges. This vulnerability leads to information disclosure, potentially allowing an attacker to harvest credentials and sensitive conversation content. In Red Hat OpenShift environments, these logs are directed to the node journal and cluster logging stack, making them accessible to any user with `pods/log` RBAC within the namespace. This persistent logging of credentials and private conversation content poses a significant risk of information disclosure. Red Hat severity: Moderate — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Weakness: CWE-538. Under investigation: Red Hat OpenShift AI (RHOAI).
Mitigation checklist
- To mitigate this issue, configure the `RUST_LOG` environment variable for the `vllm-orchestrator-gateway` component to a level higher than DEBUG, such as `INFO`. This will prevent the logging of sensitive authorization headers and full chat payloads to persistent logs. For example, set `RUST_LOG=info` in the deployment configuration. A restart of the affected pods or services is required for this change to take effect.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.