Skip to content

Security Issue #3297

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.

Sign up for GitHub

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

Jump to bottom
Closed
warpskew opened this issue Dec 29, 2016 · 2 comments
Closed

Security Issue #3297

warpskew opened this issue Dec 29, 2016 · 2 comments

Comments

@warpskew
Copy link

I'd like to reach out to the Parse team with a security issue I found on the server. I would rather not publicly post it as an issue to this repository, but I can't find another way to reach out. If there is a private alternative, please let me know. Otherwise, I have no why of reaching out.
@flovilmart
Copy link
Contributor

Reach out to me directly: florent(at)flovilmart(dot)com

@flovilmart
Copy link
Contributor

@oscarafuentes, still haven't received your mail. We take security seriously. And would be able to provide a fix ASAP.

@snyk-bot snyk-bot mentioned this issue Sep 4, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flovilmart @warpskew