Security readout for executives and security teams
This is an old Python flaw where affected versions could create temporary files with predictable names. A local user on the same system could abuse that behavior to make Python run unintended code. The risk is mainly to legacy servers or appliances still running Python 2.2.1 or earlier. Exposure is most likely on very old Linux or Unix systems, embedded appliances, or unsupported applications that still include Python 2.2.1 or earlier. Modern Python deployments are unlikely to be affected, but legacy vendor images should be checked directly. Prioritize this when legacy Python exists on shared systems or regulated environments. For modern estates, this is usually a legacy hygiene issue. The business action is inventory, upgrade or retire, and reduce local-user exposure. Mitigation focus: Identify and remove Python 2.2.1 or earlier where possible.; Apply corrected Python packages from relevant vendor advisories.; Isolate or retire systems that cannot be upgraded..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2002-1119 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
