accesscontrol@3.0.2 vulnerabilities

Security framework for Zope.

Direct Vulnerabilities

Known vulnerabilities in the accesscontrol package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Race Condition

Affected versions of this package are vulnerable to Race Condition via guarded_import when multiple requests run into the same initializing script which imports the same library.

How to fix Race Condition?

Upgrade AccessControl to version 5.3.1 or higher.

[,5.3.1)
  • M
Information Exposure

Affected versions of this package are vulnerable to Information Exposure. When the format functionality of Python is utilized, an individual controlling the format string can access objects via attribute access and subscription from accessible objects. This access uses Python's getattr and getitem, not the policy restricted AccessControl variants _getattr_ and _getitem_. This could potentially lead to critical information disclosure.

How to fix Information Exposure?

Upgrade AccessControl to version 4.4, 6.2 or higher.

[,4.4) [5.0,6.2)
  • H
Arbitrary Code Execution

accesscontrol is a Security framework for Zope2. The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

[3.0,3.0.3]
  • M
Timing Attack

accesscontrol is a Security framework for Zope2. AccessControl/AuthEncoding.py in Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain passwords via vectors involving timing discrepancies in password validation.

[3.0,3.0.5]
  • M
Insecure Randomness

accesscontrol is a Security framework for Zope2. Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, does not reseed the pseudo-random number generator (PRNG), which makes it easier for remote attackers to guess the value via unspecified vectors. NOTE: this issue was SPLIT from CVE-2012-5508 due to different vulnerability types (ADT2).

[3.0,3.0.5]