CVE-2000-1211: High severity Zope Zope vulnerability

Published 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.

Affected Software

12 affected components
pip/zope>=2.2.0<=2.2.4
Zope Zope=2.2.0b2
Zope Zope=2.2.1
Zope Zope=2.2.0b4
Zope Zope=2.2.0
Zope Zope=2.2.1b1
Zope Zope=2.2.4
Zope Zope=2.2.2
Zope Zope=2.2.0b1
Zope Zope=2.2.0b3
Zope Zope=2.2.0a1
Zope Zope=2.2.3

Event History

Dec 16, 2000
CVE Published
05:00 AM
Apr 2, 2003
CVE Published
via MITRE·05:00 AM
Data Sourced
via MITRE·05:00 AM
Description
Apr 30, 2022
Advisory Published
06:15 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2000-1211?

CVE-2000-1211 is classified as a high severity vulnerability due to its potential for unauthorized access and actions within Zope instances.

2

How do I fix CVE-2000-1211?

To resolve CVE-2000-1211, upgrade Zope to version 2.2.5 or later, which includes necessary security patches.

3

What versions of Zope are affected by CVE-2000-1211?

CVE-2000-1211 affects Zope versions from 2.2.0 through 2.2.4, including earlier beta versions.

4

What kind of attacks can exploit CVE-2000-1211?

Attackers can exploit CVE-2000-1211 to perform unauthorized operations using legacy object constructor names.

5

Is there a workaround for CVE-2000-1211 if I cannot upgrade immediately?

A temporary workaround for CVE-2000-1211 involves restricting access to Zope applications and legacy constructor names.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203