Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of empty passwords and use of HTTP #18

Open
akondasif opened this issue Jul 15, 2018 · 1 comment
Open

Use of empty passwords and use of HTTP #18

akondasif opened this issue Jul 15, 2018 · 1 comment

Comments

@akondasif
Copy link

Greetings,

I am a security researcher, who is looking for security smells in Puppet scripts. I noticed instances of empty passwords. Empty passwords increase the guessability of passwords. The Common Weakness Organization (CWE) identifies use of empty passwords as a security weakness (https://cwe.mitre.org/data/definitions/258.html).

I suggest that to follow the strong password guidelines, and manage passwords with hiera.

Any feedback is appreciated.

Source: https://github.com/poolski/puppet-beats/blob/master/manifests/outputs/elasticsearch.pp

@akondasif akondasif changed the title Use of empty passwords is a bad practice Use of empty passwords and use of HTTP Jul 15, 2018
@akondasif
Copy link
Author

I also found instances where the HTTP protocol is used instead of HTTPS (HTTP with TLS). According to the Common Weakness Enumeration organization this is a security weakness (https://cwe.mitre.org/data/definitions/319.html). I was wondering why HTTP is used? Is it because of lack of tool support?

I am trying to find out if developers are forced to adopt bad practices due to lack of tool support when it comes to the HTTPS protocol. Maybe it is due to dependency on a resource that uses HTTP?

Any feedback is appreciated.

Source: https://github.com/poolski/puppet-beats/blob/master/manifests/repo/yum.pp (Line 11)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant