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 #92

Open
JamieSlome opened this issue Feb 4, 2022 · 1 comment
Open

Found a possible security concern #92

JamieSlome opened this issue Feb 4, 2022 · 1 comment

Comments

@JamieSlome
Copy link

Hey there!

I belong to an open source security research community, and a member (@Sampaguitas) 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)

@Sampaguitas
Copy link

Sampaguitas commented Oct 25, 2023

Hey there,

I tried to get in touch with the developers of the npm package node-object-mapper to report a prototype pollution vulnerability but never got any feedback.

The latest version (6.2.0) of this package is still vulnerable.

Here is the link to the security report published on huntr.com platform.

I would appreciate if you could validate it, a patch is also available to fix the vulnerability.

With best regards,

Timothee

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

2 participants