You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the way zabbix_host is configured, it will inject $zabbix_api_pass into the resource with the property name zabbix_pass. This results in a password leak when puppet reports / resources can be inspected by third parties. At our setup, we run puppetboard without authentication. Other packages don't put clear text passwords in reports and resources, so this setup mostly works for us.
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 4.10.4
Ruby: ?
Distribution: Ubuntu 16.04
Module version: 4.1.3
How to reproduce (e.g Puppet code you use)
What are you seeing
When running the following PQL, the result includes the API credentials:
resources { type = "Zabbix_host" }
What behaviour did you expect instead
No passwords being logged.
Any additional information you'd like to impart
Other modules (e.g. puppetlabs/mongodb) write the credentials to a file (~/.mongorc.js). This way, there's no need to communicate the credentials through the resources.
The text was updated successfully, but these errors were encountered:
Currently the way
zabbix_host
is configured, it will inject$zabbix_api_pass
into the resource with the property namezabbix_pass
. This results in a password leak when puppet reports / resources can be inspected by third parties. At our setup, we run puppetboard without authentication. Other packages don't put clear text passwords in reports and resources, so this setup mostly works for us.Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
When running the following PQL, the result includes the API credentials:
What behaviour did you expect instead
No passwords being logged.
Any additional information you'd like to impart
Other modules (e.g. puppetlabs/mongodb) write the credentials to a file (
~/.mongorc.js
). This way, there's no need to communicate the credentials through the resources.The text was updated successfully, but these errors were encountered: