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

CVE for <7.1.0 references non-existent 6.2.3 release #4750

Closed
untitaker opened this issue Jul 1, 2020 · 11 comments · Fixed by #4781
Closed

CVE for <7.1.0 references non-existent 6.2.3 release #4750

untitaker opened this issue Jul 1, 2020 · 11 comments · Fixed by #4781
Labels

Comments

@untitaker
Copy link

CVE-2020-10379 references the changelog of release 6.2.3, a release that does not exist. I don't see any attempt to backport the relevant security fixes to the 6.2.x branch. Please clarify whether 6.2.3 will be released or 6.2 is EOL.

@radarhere
Copy link
Member

There was discussion about adding security patches to the 6.2.x series, since it was the last Pillow version to support Python 2.7. However, that discussion did not result in a release, and there are no active plans to do so.

@radarhere radarhere changed the title CVE for <7.1.0 references nonexistant 6.2.3 release CVE for <7.1.0 references non-existent 6.2.3 release Jul 1, 2020
@radarhere
Copy link
Member

Actually, the CVE description also references 7.0.1, which doesn't exist either. I have submitted a request to have this corrected.

@hugovk
Copy link
Member

hugovk commented Jul 4, 2020

Thanks!

The Mitre pages for the first three CVEs of #4538 say "Pillow before 6.2.3 and 7.x before 7.0.1", and the last two say "Pillow before 7.0.0".

All should say "Pillow before 7.1.0" and links to 404
https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html removed.

@graingert
Copy link

There was discussion about adding security patches to the 6.2.x series,

@radarhere is there a public link to that discussion?

@radarhere
Copy link
Member

No. It was had in a context of discussing the security vulnerabilities before the fixes had been released.

You can make your argument here, but overall, Pillow has pledged to drop support for Python 2.7 as part of https://python3statement.org/

@graingert
Copy link

graingert commented Jul 7, 2020

@radarhere I've got no argument, I was just interested to see the discussion

@untitaker
Copy link
Author

Please announce EOL of version ranges beforehand and with intent, not opportunistically. It is distressing to see support being dropped as soon as the CVE gets out.

@radarhere
Copy link
Member

radarhere commented Jul 7, 2020

The end of Python 2.7 support was announced in the Pillow 6.0.0 release notes, 9 months before support was ended.

@graingert
Copy link

graingert commented Jul 7, 2020

To be fair, those notes don't imply that 6.x will not continue to get security fixes

Pillow 6.x the last series to support Python 2.

My incorrect interpretation was that there would be continued support for v6, but no new features would be backported

chigby added a commit to freedomofpress/pressfreedomtracker.us that referenced this issue Jul 7, 2020
These are vulnerabilities related to processing of malicious images,
and since we don't expose image uploading to 3rd parties on this site,
somewhat reasonable to ignore.

There is no planned 6.2.3 release of pillow to fix this (see
python-pillow/Pillow#4750) and wagtail 2.7.x
requires this as of today.  Possibly the 2.7 branch of wagail will
relax this requirement, but until then I think it's best to ignore
these.
chigby added a commit to freedomofpress/securedrop.org that referenced this issue Jul 7, 2020
These are vulnerabilities related to processing of malicious images,
and since we don't expose image uploading to 3rd parties on this site,
somewhat reasonable to ignore.

There is no planned 6.2.3 release of pillow to fix this (see
python-pillow/Pillow#4750) and wagtail 2.7.x
requires this as of today.  Possibly the 2.7 branch of wagail will
relax this requirement, but until then I think it's best to ignore
these.
chigby added a commit to freedomofpress/securethenews that referenced this issue Jul 7, 2020
These are vulnerabilities related to processing of malicious images,
and since we don't expose image uploading to 3rd parties on this site,
somewhat reasonable to ignore.

There is no planned 6.2.3 release of pillow to fix this (see
python-pillow/Pillow#4750) and wagtail 2.7.x
requires this as of today.  Possibly the 2.7 branch of wagail will
relax this requirement, but until then I think it's best to ignore
these.
gasman added a commit to gasman/wagtail that referenced this issue Jul 10, 2020
This allows users on the 2.7 LTS branch to upgrade Pillow to address [CVE-2020-10379](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10379), as Pillow 6.x is EOL (python-pillow/Pillow#4750).
gasman added a commit to wagtail/wagtail that referenced this issue Jul 10, 2020
This allows users on the 2.7 LTS branch to upgrade Pillow to address [CVE-2020-10379](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10379), as Pillow 6.x is EOL (python-pillow/Pillow#4750).
@radarhere
Copy link
Member

@hugovk the first four CVEs have now been updated. The last one does not actually say that the problem applies 'before 7.0.0', it says that it applies 'through 7.0.0'.

@ThiefMaster
Copy link

Please backport security fixes to 6.2.x especially if it's somewhat easily possible.

In a perfect world everyone was on Python 3 right now and thus be able to use Pillow 7.x. However, the world is not perfect and there are some projects where migrating to Python 3 takes time (still happening this year) and more important where the last version that supports Python 2 is still supported for a while.

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

Successfully merging a pull request may close this issue.

5 participants