CVE-2025-3599
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 · uneditedSymantec Endpoint Protection Windows Agent, running an ERASER Engine prior to 119.1.7.8, may be susceptible to an Elevation of Privilege vulnerability, which may allow an attacker to delete resources that are normally protected from an application or user.
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 confidenceThe ERASER Engine in Symantec Endpoint Protection Windows Agent versions prior to 119.1.7.8 contains an elevation of privilege vulnerability that allows an attacker to delete resources that would normally be protected from the application's or user's standard context.
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< 119.1.7.8CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 SEP Agent versionOpen the Symantec Endpoint Protection client UI, click Help > About, or run 'smc -version' from command promptAffected if version shown is prior to 119.1.7.8
-
Check ERASER Engine version via registryNavigate to HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\Eraser in Windows Registry and read the Version valueAffected if ERASER Engine version is lower than 119.1.7.8 or the key does not exist
-
Verify ERASER Engine component is presentCheck for the presence of Eraser Engine files in the SEP installation directory (typically C:\Program Files\Symantec\Symantec Endpoint Protection\)Affected if Eraser component exists and version cannot be determined or is below 119.1.7.8
-
Confirm vulnerability applicabilityEnsure the affected SEP Agent version (prior to 119.1.7.8) is running on a Windows systemAffected if Running any version of SEP Agent prior to 119.1.7.8 with the ERASER Engine component enabled
The environment is affected if the installed Symantec Endpoint Protection ERASER Engine version is below 119.1.7.8.
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 · scoped119.1.7.8
Upgrade the ERASER Engine component of Symantec Endpoint Protection to version 119.1.7.8 or later to remediate this vulnerability.
119.1.7.8
- Open the Symantec Endpoint Protection manager console or use the deployment tool
- Navigate to the Eraser Engine update section
- Update the Eraser Engine to version 119.1.7.8 or later
- Verify the updated version by checking the Eraser Engine version in the Windows Agent
- Confirm the vulnerability is remediated by verifying the Eraser Engine version is 119.1.7.8 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3599 — 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-2025-3599 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