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

Possible Vulnerability #9

Open
HKResearch opened this issue Jul 3, 2014 · 0 comments
Open

Possible Vulnerability #9

HKResearch opened this issue Jul 3, 2014 · 0 comments

Comments

@HKResearch
Copy link

Hello,

We are conducting research on the unintended exposure of secrets in GitHub repositories. In a recent scan we conducted of GitHub repositories, our tool detected that one of your repositories appears to expose a secret, and we've confirmed this possibility by manual inspection. The details are below:

# Branch: master
## File: peerministryorg/wp-config.php
## Line: 49


# Branch: master
## File: peerministryorg/wp-config.php
## Line: 51


# Branch: master
## File: peerministryorg/wp-config.php
## Line: 50

# Branch: master
## File: peerministryorg/wp-config.php
## Line: 62


# Branch: master
## File: peerministryorg/wp-config.php
## Line: 64


# Branch: master
## File: peerministryorg/wp-config.php
## Line: 72


# Branch: master
## File: peerministryorg/wp-config.php
## Line: 63

# Branch: master
## File: peerministryorg/wp-config.php
## Line: 74


# Branch: master
## File: peerministryorg/wp-config.php
## Line: 73

If this information is indeed intended to be secret, we would recommend that you remove this file from the repository (using .gitignore) and generate new passwords for the vulnerable accounts. We would much appreciate a response, letting us know if we are mistaken in concluding that this is a secret, or if you made changes as a result of this report.

Thank you.

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