Security readout for executives and security teams
Plain-English summary
ForkLift for macOS 3.x before 3.4 allowed a local user or process to use its privileged helper to perform root-level file operations. This could let an attacker with access to the Mac escalate control over files and permissions. The sources do not show active exploitation.
Executive priority
Treat this as a high-priority endpoint hygiene issue, not an internet-facing emergency. Fix affected Macs promptly because successful abuse could give root-level file control after local compromise.
Technical view
The vulnerability is a local privilege escalation in BinaryNights ForkLift 3.x before 3.4. The privileged helper exposed an XPC interface that allowed copy, move, delete, and permission-change operations as root to any process. Public sources identify 3.4 as the security update boundary.
Likely exposure
Exposure is limited to macOS endpoints where ForkLift 3.x before 3.4 is installed. Risk is higher on shared workstations, developer machines, or managed Macs where a lower-privileged account or compromised user process could interact locally.
Exploitation context
This is not remotely exploitable based on the provided evidence. It requires local access or code running on the affected Mac. The source bundle does not cite CISA KEV listing, in-the-wild exploitation, or a public exploit campaign.
Researcher notes
Key evidence is the CVE description, BinaryNights security update reference, and an independent technical write-up. CVSS, CWE, CPE, and exploitation status are not supplied in the bundle, so severity scoring and fleet exposure require local asset data.
Mitigation direction
- Upgrade ForkLift 3.x installations to version 3.4 or later.
- Remove ForkLift from systems where it is not business-required.
- Check BinaryNights guidance for any newer security instructions.
- Prioritize managed macOS endpoints and shared workstations first.
Validation and detection
- Inventory macOS systems for ForkLift installations and versions.
- Confirm no deployed ForkLift 3.x version is below 3.4.
- Review management tooling for vulnerable app remnants or unmanaged copies.
- Check endpoint telemetry for unusual local permission or file-operation events.
Public sources used
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.
Privilege 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-15349 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://binarynights.com/blog/posts/forklift-3-4-security-update.htmlCVE reference · x_refsource_CONFIRM
- https://insinuator.net/2020/11/forklift-lpe/CVE 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.