EndgameApplication · Elastic
CVE-2022-38777
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 · uneditedAn issue was discovered in the rollback feature 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 privilege escalation vulnerability exists in the rollback feature of Elastic Endpoint Security for Windows. Unprivileged users can exploit the rollback mechanism to gain LocalSystem account privileges, achieving full administrative control over the affected endpoint.
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
EndgameApplication
< 3.62.3
Endpoint SecurityApplication
< 7.17.9>= 8.0.0, < 8.5.0CVSS 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.
-
Identify installed Elastic productCheck if Elastic Endpoint Security or Elastic Endgame is installed on the Windows endpoint by reviewing installed programs in Control Panel or via PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayNameAffected if Either Elastic Endpoint Security or Elastic Endgame is installed
-
Determine Elastic Endgame versionIf Elastic Endgame is present, retrieve its version by checking the file version of the endgame.exe binary, typically located in the Elastic installation directory, or via PowerShell: Get-ItemProperty 'C:\Program Files\Elastic\Endgame\endgame.exe' | Select-Object VersionInfoAffected if The installed Elastic Endgame version is lower than 3.62.3
-
Determine Elastic Endpoint Security versionIf Elastic Endpoint Security is present, retrieve its version by checking the file version of the endpoint-protection.exe binary in the Elastic installation directory, or via PowerShell: Get-ItemProperty 'C:\Program Files\Elastic\Endpoint Security\endpoint-protection.exe' | Select-Object VersionInfoAffected if The installed Elastic Endpoint Security version is lower than 7.17.9, or is 8.0.0 or higher but lower than 8.5.0
You are affected if Elastic Endgame version is below 3.62.3, or Elastic Endpoint Security version is below 7.17.9 or between 8.0.0 and 8.5.0, and the rollback feature is accessible to unprivileged users on the endpoint.
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 · scoped3.62.37.17.98.5.0
Apply the vendor patch for CVE-2022-38777 when available. In the interim, restrict physical access to endpoints and monitor for suspicious rollback feature usage by non-admin accounts.
Endgame: 3.62.3+ | Endpoint Security: 7.17.9+ or 8.5.0+
- Identify which Elastic product is installed: Endgame or Endpoint Security
- For Endgame users: Upgrade to version 3.62.3 or later
- For Endpoint Security users: If using version 7.x, upgrade to 7.17.9 or later; if using version 8.x, upgrade to 8.5.0 or later
- Verify the upgrade was successful by checking the product version in the Elastic security console
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Endgame
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38777 — 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-38777 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