CVE-2011-4211: n/a vulnerability

CVE-2011-4211: The FakeFile implementation in the sandbox environment in the Google App Engine Python SDK before 1.5.4 doe...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 00:01 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2011-4211 affects old Google App Engine Python SDK versions before 1.5.4. A sandbox file-handling weakness could let local users bypass intended restrictions and create arbitrary files through the SDK admin interactive execution path. This mainly matters where legacy SDK tooling is still installed or exposed. Exposure is most likely in legacy development, test, or administrative environments still using Google App Engine Python SDK versions before 1.5.4. The provided sources do not identify cloud-hosted production App Engine services as affected. Treat this as a legacy tooling exposure, not an internet-scale emergency based on the provided evidence. Prioritize remediation if old App Engine Python SDK tooling exists on shared developer hosts, CI systems, or environments where untrusted users have access. Mitigation focus: Inventory systems for Google App Engine Python SDK versions before 1.5.4.; Upgrade affected SDK installations to 1.5.4 or later where applicable.; Restrict access to SDK administrative interactive execution interfaces..

Prepared: Jun 27, 2026, 17:48 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-4211 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Oct 30, 2011, 19:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
google-app-fakefile-priv-esc(71064)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.