Security readout for executives and security teams
Apache Oozie versions before 5.2.1 have a race condition during sharelib creation. A malicious actor could replace files in Oozie's sharelib at that moment, creating local privilege-escalation risk. The public sources do not provide CVSS scoring or evidence of active exploitation. Organizations running Apache Oozie before 5.2.1 are the relevant exposure group. Risk is most likely in Hadoop/Oozie environments where users or processes can influence local filesystem state during sharelib creation. The bundle does not identify affected operating systems, distributions, or managed services. Treat this as a targeted infrastructure hardening item, not an emergency internet-wide incident. Prioritize Oozie clusters with multiple users, delegated administration, or shared filesystem access, and plan upgrade or compensating controls if versions are before 5.2.1. Mitigation focus: Upgrade Apache Oozie to version 5.2.1 or later where applicable.; Review Apache Oozie advisory guidance before changing production clusters.; Restrict local and administrative access to Oozie hosts..
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.
CWE-377: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-35451 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
- https://lists.apache.org/thread.html/r8688debdb8b586aab3e53dee2d675fc9212de0ec627a8d3cd43b5ab5%40%3Cuser.oozie.apache.org%3ECVE reference · x_refsource_MISC
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.
Insecure Temporary File
Insecure Temporary File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.