Endpoint SecurityApplication · Elastic
CVE-2022-23714
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA local privilege escalation (LPE) issue was discovered in the ransomware canaries features of Elastic Endpoint Security for Windows, which could allow unprivileged users to elevate their privileges to those of the LocalSystem account.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability exists in the ransomware canaries feature of Elastic Endpoint Security for Windows. The issue allows unprivileged users to gain LocalSystem privileges through improper access control in the canary file handling mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Endpoint SecurityApplication
>= 7.13.0, <= 7.17.4>= 8.0.0, <= 8.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Elastic Endpoint Security installationCheck if Elastic Endpoint Security is installed on the Windows system by looking for the service 'Elastic Endpoint' in Services.msc, or check for the installation directory typically at C:\Program Files\Elastic\Endpoint or C:\Program Files\Elastic\Elastic Endpoint\Affected if The Elastic Endpoint service is running and the software is present on the system
-
Determine installed versionOpen Programs and Features in Control Panel and find 'Elastic Endpoint Security' in the list, or right-click the Elastic Endpoint tray icon and select 'About' to view the version numberAffected if The installed version falls within 7.13.0 through 7.17.4 OR 8.0.0 through 8.2.3
-
Confirm ransomware canaries feature is activeOpen Elastic Endpoint Security configuration or policy settings. The canaries feature is typically enabled by default as part of ransomware protection. Check if 'Canary Files' or 'Ransomware Canaries' are configured in the endpoint security policy.Affected if The ransomware canaries feature is enabled in the Elastic Endpoint policy (this is required for the vulnerability to be exploitable)
-
Inspect canary file permissionsLocate the canary files created by Elastic Endpoint. These are typically hidden files in user-accessible directories such as %USERPROFILE%\Documents, %USERPROFILE%\Downloads, or %USERPROFILE%\Desktop. Use 'icacls <filename>' to check file permissions. Look for whether low-privileged users have write or modify access to these canary files.Affected if Standard user accounts have write, modify, or full control permissions on the canary files rather than restricted permissions
The system is affected if Elastic Endpoint Security version 7.13.0-7.17.4 or 8.0.0-8.2.3 is installed with the ransomware canaries feature enabled and canary files have improper access control permissions allowing unprivileged modification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor-supplied patch or upgrade to a patched version of Elastic Endpoint Security for Windows to remediate this privilege escalation vulnerability.
7.17.5+ or 8.2.4+ (latest respective 7.x or 8.x release)
- 1. Identify the currently installed Elastic Endpoint Security version by checking the application or using system inventory tools
- 2. For versions 7.13.0 through 7.17.4: Upgrade to version 7.17.5 or later (preferably the latest 7.x stable release)
- 3. For versions 8.0.0 through 8.2.3: Upgrade to version 8.2.4 or later (preferably the latest 8.x stable release)
- 4. Download the updated Elastic Endpoint Security installer from the official Elastic download page at www.elastic.co/downloads/endpoints
- 5. Run the installer with administrative privileges to apply the update
- 6. Verify the upgrade was successful by checking the Endpoint Security version in the Elastic Endpoint application or management console
- 7. Confirm the ransomware canaries feature is functioning correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Endpoint Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23714 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data