CVE-2023-35077
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 out-of-bounds write vulnerability on windows operating systems causes the Ivanti AntiVirus Product to crash. Update to Ivanti AV Product version 7.9.1.285 or above.
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 · high confidenceAn out-of-bounds write vulnerability exists in Ivanti AntiVirus on Windows operating systems, where the software writes data beyond allocated memory buffer boundaries, leading to memory corruption and application crash.
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< 7.9.1.285CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm Ivanti Endpoint Manager is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Ivanti Endpoint Manager' in the installed programs listAffected if Ivanti Endpoint Manager is not present in the installed programs list, then the system is not affected
-
Check the installed version of Ivanti Endpoint ManagerIn the Windows Control Panel > Programs and Features, select Ivanti Endpoint Manager and view the Version column, or run 'reg query "HKLM\SOFTWARE\LANDesk\LDWS\Core\CurrentVersion" /v Version' in Command PromptAffected if The version number is lower than 7.9.1.285 (for example, 7.9.1.200 or earlier), then the system is affected
-
Verify the Ivanti AntiVirus module is enabledOpen Ivanti Endpoint Manager client, navigate to the AntiVirus or Security settings panel, or check the Windows Services console (services.msc) for the 'Ivanti AntiVirus Service' or 'LANDesk AntiVirus' service statusAffected if The AntiVirus service is running or the AntiVirus module is enabled in the client, then the vulnerability is present and potentially exploitable; if the AntiVirus component is completely disabled or not installed, exploitation may not be possible
The system is affected by CVE-2023-35077 if Ivanti Endpoint Manager version is lower than 7.9.1.285 AND the AntiVirus component is installed and enabled.
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 · scoped7.9.1.285
Update Ivanti AntiVirus to version 7.9.1.285 or above to address the vulnerability.
7.9.1.285 or later
- 1. Back up the current Ivanti Endpoint Manager configuration and database according to vendor best practices
- 2. Download Ivanti Endpoint Manager version 7.9.1.285 or later from the official Ivanti download portal or support site
- 3. Review the Ivanti upgrade documentation and release notes for version 7.9.1.285 before proceeding
- 4. Apply the upgrade in a test/staging environment first to validate compatibility
- 5. Execute the upgrade following the standard Ivanti installation/upgrade procedure for your deployment mode
- 6. After upgrade, verify that the Ivanti AntiVirus component is running version 7.9.1.285 or higher
- 7. Confirm that the out-of-bounds write vulnerability is resolved and the antivirus functionality is operating normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35077 — 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-2023-35077 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