REDHAT-BUG-2528255: High severity Ansible AWX vulnerability
Controller registers LOGAGGREGATORHOST as a bare CharField with no character validation, and the logging settings validator only verifies that host/type are present. When any LOGAGGREGATOR setting is changed via PATCH /api/controller/v2/settings/logging/ (superuser-only), Controller regenerates /var/lib/awx/rsyslog/rsyslog.conf and restarts awx-rsyslogd. In the tcp/udp (omfwd) code path the host value is written raw as target="{host}", allowing an attacker to close the action() statement and append module(load="omprog") plus an omprog action() whose binary= runs an arbitrary shell command in the rsyslog control-plane component (uid=awx). That process can read SECRETKEY and the Postgres credentials, decrypt every stored Credential, and forge inter-service JWTs. Upstream: https://github.com/ansible/awx (devel) — UNFIXED (no PR) Affected file: awx/main/utils/externallogging.py (constructrsyslogconftemplate: :26 spoolDirectory, :100 errorfile, :128 target); awx/main/conf.py (:565-574, :958-979); awx/conf/views.py (:131-133)
Affected Software
Event History
Frequently Asked Questions
What level of access is required to exploit this issue?
An attacker needs superuser access to change LOG_AGGREGATOR settings through PATCH /api/controller/v2/settings/logging/. The vulnerable path is reached when a LOG_AGGREGATOR* setting is changed.
Is an upstream fix available?
No. The upstream AWX development branch is identified as unfixed, with no pull request available.