LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1665: The XML libraries for Python 3.4, 3.3, 3.2, 3.1, 2.7, and 2.6, as used in OpenStack Keystone Essex and Fols...

The XML libraries for Python 3.4, 3.3, 3.2, 3.1, 2.7, and 2.6, as used in OpenStack Keystone Essex and Folsom, Django, and possibly other products allow remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, aka an XML External Entity (XXE) attack.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-1665 is an XML External Entity issue in Python XML libraries used by Python 2.6, 2.7, and 3.1 through 3.4. If an application accepts attacker-controlled XML, a remote attacker may cause the service to read local files. OpenStack Keystone Essex and Folsom, Django, and possibly other products were cited as affected contexts. Exposure is most likely in legacy Python services or frameworks that parse XML supplied by users, integrations, APIs, identity systems, or message feeds. The source bundle names OpenStack Keystone Essex/Folsom and Django, but affected deployment scope depends on whether vulnerable Python XML parsing is reachable with untrusted XML. Treat as high priority for legacy internet-facing or identity-related systems that parse XML. The issue can expose sensitive local files, including configuration or credential material, but urgency is lower where vulnerable Python versions are retired or XML parsing is not reachable by untrusted users. Mitigation focus: Apply relevant vendor updates from Python, OpenStack, Red Hat, Ubuntu, or Debian guidance.; Replace unsafe Python XML parsing with defusedxml where vendor guidance supports it.; Disable external entity resolution in XML parsers that handle untrusted input..

Prepared

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-2013-1665 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
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

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.