CVE-2023-4814
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 Privilege escalation vulnerability exists in Trellix Windows DLP endpoint for windows which can be abused to delete any file/folder for which the user does not have permission to.
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 confidenceTrellix Windows DLP endpoint contains a privilege escalation vulnerability that allows authenticated users to delete files or folders for which they lack permissions, effectively bypassing intended access controls.
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= 11.10.100.17CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm Trellix DLP installationCheck for Trellix Data Loss Prevention endpoint agent on the Windows system by reviewing installed programs in Control Panel or using 'Get-WmiObject -Class Win32_Product' or reviewing the program directoryAffected if Trellix DLP endpoint software is not found on the system, the vulnerability does not apply
-
Identify installed Trellix DLP versionLocate the version information for the Trellix DLP agent - this is typically visible in Add/Remove Programs, the DLP agent UI, or can be queried via the DLP management consoleAffected if The installed version is exactly 11.10.100.17, indicating the specific affected release
-
Cross-reference version with vendor advisoryCompare your identified Trellix DLP version against the affected version range in the CVE advisory (11.10.100.17)Affected if The version matches the exact affected version 11.10.100.17, meaning the environment contains the vulnerable configuration
-
Verify DLP endpoint agent is activeConfirm the Trellix DLP endpoint service or agent process is currently running on the systemAffected if The DLP agent is installed and running with the vulnerable version, exposing the privilege escalation condition
The environment is affected only if Trellix Data Loss Prevention endpoint version 11.10.100.17 is installed and active, enabling authenticated users to bypass file deletion access controls.
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.
From vendor dataApply vendor-supplied patches or updates for Trellix Windows DLP endpoint when available; otherwise, restrict administrative access to the DLP agent and monitor for unauthorized file deletion activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4814 — 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-4814 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