VYPR
Unrated severityNVD Advisory· Published Jan 9, 2024· Updated Jun 3, 2025

CVE-2023-50643

CVE-2023-50643

Description

Evernote for macOS 10.68.2 allows code injection via Electron fuses, but requires prior system access.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Evernote for macOS 10.68.2 allows code injection via Electron fuses, but requires prior system access.

Vulnerability

CVE-2023-50643 reports that Evernote for macOS v10.68.2 leaves the Electron fuses runAsNode and enableNodeCliInspectArguments enabled, which could allow an attacker to execute arbitrary code. The Electron project disputes the severity, stating the configuration does not enable remote code execution and that an attacker must already have command execution ability on the system [1][3].

Exploitation

Exploitation requires the attacker to already have arbitrary command execution on the target machine (e.g., physical access or prior RCE). A proof-of-concept tool (electroniz3r) can validate the vulnerable fuse state and inject code to obtain a shell [3]. No user interaction is needed beyond the initial compromise.

Impact

Successful exploitation allows arbitrary code execution within the Evernote app context, potentially leading to full system compromise. However, the attacker must already have significant access to the system, limiting the practical impact [1][3].

Mitigation

Evernote has not officially announced a fix; the issue is disputed. Users should update to the latest version of Evernote (if available) and ensure Electron fuses are disabled. The Electron project recommends disabling these fuses for security. No workarounds are provided if a patch is not installed [1].

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.