Possible Vulnerability

[HKResearch]

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: portfolio/publish/blog/wp-config.php
## Line: 22


# Branch: master
## File: portfolio/publish/blog/wp-config.php
## Line: 28


# Branch: master
## File: portfolio/publish/blog/wp-config.php
## Line: 25

# Branch: master
## File: portfolio/blog/wp-config.php
## Line: 22


# Branch: master
## File: portfolio/blog/wp-config.php
## Line: 28


# Branch: master
## File: portfolio/blog/wp-config.php
## Line: 25

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.

[jkarpala]

Hi,

Thank you,

I've remove the two files from the repository

thanks,
Jeff

On Thu, Jul 3, 2014 at 2:55 PM, HKResearch notifications@github.com wrote:

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: portfolio/publish/blog/wp-config.php

Line: 22

Branch: master

File: portfolio/publish/blog/wp-config.php

Line: 28

Branch: master

File: portfolio/publish/blog/wp-config.php

Line: 25

Branch: master

File: portfolio/blog/wp-config.php

Line: 22

Branch: master

File: portfolio/blog/wp-config.php

Line: 28

Branch: master

File: portfolio/blog/wp-config.php

Line: 25

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.

—
Reply to this email directly or view it on GitHub
#1.