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

Found a possible security concern #491

Closed
JamieSlome opened this issue Apr 8, 2022 · 2 comments
Closed

Found a possible security concern #491

JamieSlome opened this issue Apr 8, 2022 · 2 comments

Comments

@JamieSlome
Copy link

Hey there!

I belong to an open source security research community, and a member (@salmonx) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

@lcrilly
Copy link

lcrilly commented Apr 8, 2022

Please report any security-related issues concerning njs to security-alert@nginx.org. For our mutual convenience, specifically mention njs in the subject and follow the CVSS v3.1 specification.

See https://nginx.org/en/security_advisories.html for confirmation of the contact method.

@JamieSlome
Copy link
Author

Thanks for your response @lcrilly 👍

We have just sent an e-mail to the elected address. We do follow the CVSS specification which can be found in the report.

Let me know if you have any questions and I will be happy to help!

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

No branches or pull requests

3 participants