Описание
A flaw was found in the community.general Ansible collection's jenkins_credential module. When creating a Jenkins API token (credential_type: token), the module correctly protects the input password with no_log=True in the argument specification, but places the generated API token returned by the Jenkins API directly into the Ansible task result dictionary without output suppression. The token is emitted in plaintext via exit_json(), causing it to appear in Ansible task output, AWX/Tower/AAP Controller job logs, callback plugin output, CI/CD pipeline logs, and fact caching backends. An attacker with access to any of these output channels can obtain the Jenkins API token and gain the same privileges as the user who created it.
Меры по смягчению последствий
- Add no_log: true at the task level when using the jenkins_credential module with credential_type: token:
- name: Create Jenkins API token community.general.jenkins_credential: credential_type: token jenkins_url: "{{ jenkins_url }}" jenkins_user: "{{ jenkins_user }}" jenkins_password: "{{ jenkins_password }}" register: token_result no_log: true
- Review AWX/Tower/AAP Controller job logs, CI/CD pipeline logs, and callback plugin output for any previously leaked Jenkins API tokens. Rotate any tokens found in logs.
- If fact caching is enabled, check the cache backend for registered variables containing jenkins_credential results.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | rhel-system-roles | Not affected | ||
| Red Hat Enterprise Linux 8 | rhc-worker-playbook | Not affected | ||
| Red Hat Enterprise Linux 8 | rhel-system-roles | Not affected | ||
| Red Hat Enterprise Linux 9 | rhel-system-roles | Not affected |
Показывать по
Дополнительная информация
Статус:
6.1 Medium
CVSS3
Связанные уязвимости
6.1 Medium
CVSS3