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

Multiple memory corruption vulnerabilities #2105

Closed
cneckar opened this issue Sep 6, 2016 · 13 comments

Comments

Projects
None yet
5 participants
@cneckar
Copy link

commented Sep 6, 2016

While performing a security assessment for a client, we identified a number of potential memory corruption vulnerabilities within the native extensions included with Pillow. Given that these vulnerabilities may currently expose exploitable conditions within our client's environment, we would like to report the details privately.

Could a project member please limit the visibility of this issue so that it is not available to the public?

Alternatively, we can provide vulnerability details via e-mail if that is preferable.

Thank you,
Cris Neckar
Divergent Security

@hugovk

This comment has been minimized.

Copy link
Member

commented Sep 6, 2016

Hi Cris,

Thanks for getting in touch. We can't make this issue private, but please email aclark@aclark.net

https://github.com/python-pillow/Pillow/blob/master/.github/CONTRIBUTING.md#security-vulnerabilities

Edit: you can also email security@python-pillow.org (#1713 (comment))

@cneckar

This comment has been minimized.

Copy link
Author

commented Sep 6, 2016

@hugovk, thanks for the info. I will send details today.

@wiredfool

This comment has been minimized.

Copy link
Member

commented Sep 6, 2016

Security@ is better, since it skips the step of @aclark4life forwarding it to me.

@cneckar

This comment has been minimized.

Copy link
Author

commented Sep 6, 2016

@wiredfool

This comment has been minimized.

Copy link
Member

commented Sep 6, 2016

I was going to say yes, but apparently it's not doing that right now.

@aclark4life

This comment has been minimized.

Copy link
Member

commented Sep 6, 2016

Should be working, check your spam folder? I'll forward just in case.

@aclark4life

This comment has been minimized.

Copy link
Member

commented Sep 7, 2016

Oh, I think see what happened: I forgot I had to maintain a security@aclark.net group in Google Apps; since python-pillow.org is a domain alias for aclark.net, mail sent to security@python-pillow.org is delivered to security@aclark.net. When I recently removed that group, I still got the security mail because I receive all mail via catch-all. I think I fixed it, will send another test. I've also marked the group "Pillow Security" for future forgetfulness-proofing.

@cneckar

This comment has been minimized.

Copy link
Author

commented Sep 20, 2016

Just wanted to follow-up quickly and make sure that all of the details got
to the right people. Is there anything else that you need from us?

We are also more than happy to help in any way we can.

Thanks!
Cris Neckar
Divergent Security, LLC

On Wed, Sep 7, 2016 at 4:43 AM, Alex Clark notifications@github.com wrote:

Oh, I think see what happened: I forgot I had to maintain a
security@aclark.net group in Google Apps; since python-pillow.org is a
domain alias for aclark.net, mail sent to security@python-pillow.org is
delivered to security@aclark.net. When I recently removed that group, I
still got the security mail because I receive all mail via catch-all. I
think I fixed it, will send another test. I've also marked the group
"Pillow Security" for future forgetfulness-proofing.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2105 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKwLDg5LQ4mzCQwBobO8nYRwe7hp89mXks5qnqNegaJpZM4J2F1X
.

@wiredfool

This comment has been minimized.

Copy link
Member

commented Sep 20, 2016

Yep, I've got it, we'll definitely have something by the next release, scheduled for Oct 1. I'll probably issue a source only point release for 3.3.x as well.

@cneckar

This comment has been minimized.

Copy link
Author

commented Sep 20, 2016

Perfect! Thanks for the update.

On Tue, Sep 20, 2016 at 9:27 AM, wiredfool notifications@github.com wrote:

Yep, I've got it, we'll definitely have something by the next release,
scheduled for Oct 1. I'll probably issue a source only point release for
3.3.x as well.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2105 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKwLDtltSIxokunOBU6l7kii_YyavOpfks5qsAmAgaJpZM4J2F1X
.

@wiredfool wiredfool modified the milestone: 3.4.0 Sep 22, 2016

wiredfool added a commit that referenced this issue Oct 3, 2016

@homm

This comment has been minimized.

Copy link
Member

commented Oct 3, 2016

Fixed and released, right?

@wiredfool

This comment has been minimized.

Copy link
Member

commented Oct 3, 2016

Yep, in both 3.4.0 and 3.3.2

@wiredfool wiredfool closed this Oct 3, 2016

@hugovk

This comment has been minimized.

Copy link
Member

commented Oct 3, 2016

For future reference, here's the PR: #2146

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.