For your digest
zope: Zope Server vulnerable to DoS via header injection
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
zope (PyPI)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- zope (PyPI): from 2.0.0, before 2.4.4b2
- zope (PyPI): from 2.5.0, before 2.5.1b2
- zope (PyPI): from 2.0.0, before 2.4.4b2; from 2.5.0, before 2.5.1b2
The fix
zope (PyPI) fixed in 2.4.4b2
pippython -m pip install zope==2.4.4b2uvuv add zope==2.4.4b2poetrypoetry add zope@2.4.4b2Check what is installedpython -m pip show zopePaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope to 2.4.4b2 or the nearest later release, to fix CVE-2002-0687. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.zope (PyPI) fixed in 2.5.1b2
pippython -m pip install zope==2.5.1b2uvuv add zope==2.5.1b2poetrypoetry add zope@2.5.1b2Check what is installedpython -m pip show zopePaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency zope to 2.5.1b2 or the nearest later release, to fix CVE-2002-0687. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".