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 marked as problematic has been reported in Google App Engine Python SDK up to 1.0.1. This affects an unknown part of the component Access Restriction. Performing a manipulation of the argument code results in access control. This vulnerability is cataloged as CVE-2011-4213. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Google App Engine Python SDK up to 1.0.1 (Programming Language Software). This affects an unknown code of the component Access Restriction. The manipulation of the argument code with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The sandbox environment in the Google App Engine Python SDK before 1.5.4 does not properly prevent use of the os module, which allows local users to bypass intended access restrictions and execute arbitrary commands via a file_blob_storage.os reference within the code parameter to _ah/admin/interactive/execute, a different vulnerability than CVE-2011-1364.
The weakness was shared 10/30/2011 with Google as tp://co (Website). It is possible to read the advisory at code.google.com. This vulnerability is uniquely identified as CVE-2011-4213 since 10/30/2011. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Upgrading to version 1.0.2 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (71062) and SecurityFocus (BID 50465†). The entries VDB-3516, VDB-47987, VDB-47513 and VDB-50835 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for 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/11/2011 🔍10/30/2011 🔍
10/30/2011 🔍
10/30/2011 🔍
03/23/2015 🔍
01/28/2018 🔍
Sources
Vendor: google.comAdvisory: tp://co
Organization: Google
Status: Confirmed
CVE: CVE-2011-4213 (🔍)
GCVE (CVE): GCVE-0-2011-4213
GCVE (VulDB): GCVE-100-59259
X-Force: 71062 - Google App Engine Python SDK os module privilege escalation
SecurityFocus: 50465 - Google App Engine SDK Local Arbitrary Command Execution Vulnerability
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 01/28/2018 09:58
Changes: 03/23/2015 16:50 (51), 01/28/2018 09:58 (9)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.