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

Trying to get in touch regarding a security issue #158

Open
JamieSlome opened this issue Sep 19, 2021 · 4 comments
Open

Trying to get in touch regarding a security issue #158

JamieSlome opened this issue Sep 19, 2021 · 4 comments

Comments

@JamieSlome
Copy link

Hey there!

I'd like to report a security issue but cannot find contact instructions on your repository.

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)

@holblin
Copy link

holblin commented May 26, 2022

@JamieSlome how could we get in touch. I'm interested to know the issue for our projects.

@JamieSlome
Copy link
Author

@holblin - I will respond to your e-mail 👍

@jogibear9988
Copy link

@holblin is the issue fixed in your fork?

@holblin
Copy link

holblin commented Feb 22, 2023

I tried to contact them to have details. Except for asking meeting, I didn't receive any details of a security issue.
It might be fixed due to the changes I have done on regex and I think it might be something related to that. I don't see how this could be used or leveraged for attacks except maybe DOS but a lot of the consumers of the package (if not all) would not be impacted.

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

3 participants