Google App Engine Python SDK up to 1.0.1 Access Restriction code access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Google App Engine Python SDK up to 1.0.1. Affected by this vulnerability is an unknown functionality of the component Access Restriction. This manipulation of the argument code causes access control. This vulnerability is tracked as CVE-2011-4211. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Google App Engine Python SDK up to 1.0.1 (Programming Language Software). Affected by this vulnerability is some unknown functionality of the component Access Restriction. The manipulation of the argument code with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The FakeFile implementation in the sandbox environment in the Google App Engine Python SDK before 1.5.4 does not properly control the opening of files, which allows local users to bypass intended access restrictions and create arbitrary files via ALLOWED_MODES and ALLOWED_DIRS changes within the code parameter to _ah/admin/interactive/execute, a different vulnerability than CVE-2011-1364.
The weakness was disclosed 10/30/2011 as tp://co (Website). The advisory is shared at code.google.com. This vulnerability is known as CVE-2011-4211 since 10/30/2011. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 1.0.2 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (71064) and SecurityFocus (BID 50464†). The entries VDB-3516, VDB-47987, VDB-47513 and VDB-50835 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.4
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: App Engine Python SDK 1.0.2
Timeline
10/30/2011 🔍10/30/2011 🔍
10/30/2011 🔍
11/01/2011 🔍
03/23/2015 🔍
01/22/2018 🔍
Sources
Vendor: google.comAdvisory: tp://co
Status: Confirmed
CVE: CVE-2011-4211 (🔍)
GCVE (CVE): GCVE-0-2011-4211
GCVE (VulDB): GCVE-100-59257
X-Force: 71064 - Google App Engine Python SDK FakeFile privilege escalation
SecurityFocus: 50464 - Google App Engine Python SDK 'FakeFile' Object Local Security Bypass Vulnerability
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 01/22/2018 08:11
Changes: 03/23/2015 16:50 (53), 01/22/2018 08:11 (6)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.