CVE-2002-0170
First published: Mon Apr 22 2002(Updated: )
Zope 2.2.0 through 2.5.1 does not properly verify the access for objects with proxy roles, which could allow some users to access documents in violation of the intended configuration.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/zope | >=2.5.0<2.5.1 | 2.5.1 |
| pip/zope | >=2.2.0<2.4.4 | 2.4.4 |
| Zope ZODB | =2.2.0 | |
| Zope ZODB | =2.2.1 | |
| Zope ZODB | =2.2.2 | |
| Zope ZODB | =2.2.3 | |
| Zope ZODB | =2.2.4 | |
| Zope ZODB | =2.2.5 | |
| Zope ZODB | =2.3.0 | |
| Zope ZODB | =2.3.1 | |
| Zope ZODB | =2.3.2 | |
| Zope ZODB | =2.3.3 | |
| Zope ZODB | =2.4.0 | |
| Zope ZODB | =2.4.1 | |
| Zope ZODB | =2.4.2 | |
| Zope ZODB | =2.4.3 | |
| Zope ZODB | =2.4.4b1 | |
| Zope ZODB | =2.5.0 | |
| Zope ZODB | =2.5.1b1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.zope.org/Products/Zope/hotfixes/
- http://www.redhat.com/support/errata/RHSA-2002-060.html
- http://www.iss.net/security_center/static/8334.php
- http://www.securityfocus.com/bid/4229
- http://www.osvdb.org/5350
- http://marc.info/?l=bugtraq&m=101503023511996&w=2
- https://nvd.nist.gov/vuln/detail/CVE-2002-0170
- https://launchpad.net/zope2/+milestone/2.4.4
- https://launchpad.net/zope2/+milestone/2.5.1
- https://web.archive.org/web/20021120034302/http://online.securityfocus.com/bid/4229
- https://web.archive.org/web/20070914020022/http://xforce.iss.net/xforce/xfdb/8334
- https://github.com/advisories/GHSA-c3rp-4cjh-cp38 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2002-0170?
CVE-2002-0170 is considered a high severity vulnerability due to the potential for unauthorized access to sensitive documents.
How do I fix CVE-2002-0170?
To fix CVE-2002-0170, you should upgrade Zope to version 2.5.2 or later, which includes the necessary patches.
What versions of Zope are affected by CVE-2002-0170?
CVE-2002-0170 affects Zope versions 2.2.0 through 2.5.1.
What are the consequences of not addressing CVE-2002-0170?
Failing to address CVE-2002-0170 could lead to unauthorized users gaining access to restricted documents and potentially sensitive information.
Is there a workaround for CVE-2002-0170?
While upgrading is the recommended course of action, temporarily restricting user access until the software is updated can act as a mitigative measure.
- agent/type
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-c3rp-4cjh-cp38
- alias/CVE-2002-0170
- agent/software-canonical-lookup
- agent/severity
- agent/references
- agent/weakness
- agent/remedy
- agent/description
- agent/softwarecombine
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- collector/nvd-historical
- agent/author
- package-manager/pip
- vendor/zope
- canonical/zope zodb
- version/zope zodb/2.2.0
- version/zope zodb/2.2.1
- version/zope zodb/2.2.2
- version/zope zodb/2.2.3
- version/zope zodb/2.2.4
- version/zope zodb/2.2.5
- version/zope zodb/2.3.0
- version/zope zodb/2.3.1
- version/zope zodb/2.3.2
- version/zope zodb/2.3.3
- version/zope zodb/2.4.0
- version/zope zodb/2.4.1
- version/zope zodb/2.4.2
- version/zope zodb/2.4.3
- version/zope zodb/2.4.4b1
- version/zope zodb/2.5.0
- version/zope zodb/2.5.1b1