First published: Sat Dec 16 2000(Updated: )
Zope 2.2.0 through 2.2.4 does not properly perform security registration for legacy names of object constructors such as DTML method objects, which could allow attackers to perform unauthorized activities.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/zope | >=2.2.0<=2.2.4 | |
Zope ZODB | =2.2.0b2 | |
Zope ZODB | =2.2.1 | |
Zope ZODB | =2.2.0b4 | |
Zope ZODB | =2.2.0 | |
Zope ZODB | =2.2.1b1 | |
Zope ZODB | =2.2.4 | |
Zope ZODB | =2.2.2 | |
Zope ZODB | =2.2.0b1 | |
Zope ZODB | =2.2.0b3 | |
Zope ZODB | =2.2.0a1 | |
Zope ZODB | =2.2.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2000-1211 is classified as a high severity vulnerability due to its potential for unauthorized access and actions within Zope instances.
To resolve CVE-2000-1211, upgrade Zope to version 2.2.5 or later, which includes necessary security patches.
CVE-2000-1211 affects Zope versions from 2.2.0 through 2.2.4, including earlier beta versions.
Attackers can exploit CVE-2000-1211 to perform unauthorized operations using legacy object constructor names.
A temporary workaround for CVE-2000-1211 involves restricting access to Zope applications and legacy constructor names.