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

Audit CVEs of nginx, haproxy, etc. #6592

Closed
htuch opened this issue Apr 15, 2019 · 9 comments
Closed

Audit CVEs of nginx, haproxy, etc. #6592

htuch opened this issue Apr 15, 2019 · 9 comments
Assignees
Labels
area/security stale stalebot believes this issue/PR has not been touched recently

Comments

@htuch
Copy link
Member

htuch commented Apr 15, 2019

Nginx already had a CVE for path normalization https://www.rapid7.com/db/vulnerabilities/nginx-cve-2009-3898 similar to CVE-2019-9901. What other CVEs exist for similar classes of proxy to Envoy?

Ideally we should audit existing CVEs and track the release of new ones to verify we don't have similar issues.

Action item for CVE-2019-9901

@htuch htuch removed the help wanted Needs help! label May 1, 2019
@htuch
Copy link
Member Author

htuch commented May 1, 2019

@yanavlasov as discussed this morning, this would teach us a lot about the topography of this domain.

@stale
Copy link

stale bot commented May 31, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label May 31, 2019
@htuch
Copy link
Member Author

htuch commented May 31, 2019

@yanavlasov do you reckon we will be able to externalize your work on this?

@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label May 31, 2019
@yanavlasov
Copy link
Contributor

Yes, I think so. Let's discuss on Monday.

@stale
Copy link

stale bot commented Jun 30, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Jun 30, 2019
@stale
Copy link

stale bot commented Jul 8, 2019

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Jul 8, 2019
@htuch htuch reopened this Jul 9, 2019
@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Jul 9, 2019
@htuch
Copy link
Member Author

htuch commented Jul 9, 2019

@yanavlasov did you have some further thoughts on how to externalize your audit work?

@stale
Copy link

stale bot commented Aug 8, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Aug 8, 2019
@stale
Copy link

stale bot commented Aug 15, 2019

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

2 participants