dbcve.org
Data Loss PreventionApplication · Trellix

CVE-2023-0400

HIGH · 8.2 CVSS v3.1 Published 2023-02-02
Fix available
A fix is available. Upgrade to 11.10.0 or later.
See remediation →
82/100
Remediation priority · High

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 · unedited
The protection bypass vulnerability in DLP for Windows 11.9.x is addressed in version 11.10.0. This allowed a local user to bypass DLP controls when uploading sensitive data from a mapped drive into a web email client. Loading from a local driver was correctly prevented. Versions prior to 11.9 correctly detected and blocked the attempted upload of sensitive data.

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 confidence

DLP for Windows version 11.9.x contained a protection bypass vulnerability where sensitive data uploaded from mapped drives to web email clients was not detected or blocked, while uploads from local drives were correctly prevented. This represented a regression from earlier versions (prior to 11.9) that properly blocked both scenarios.

MitigationUpgrade DLP for Windows to version 11.10.0 or later to restore proper scanning of mapped drive content during web email uploads.

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
Data Loss PreventionApplication
Affected:>= 11.9.0, < 11.10.0

CVSS 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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed DLP version
    Check the installed version of Trellix Data Loss Prevention for Windows through the product UI, registry, or installed programs list. Compare it to the affected range: 11.9.0 through any version less than 11.10.0.
    Affected if The installed version is 11.9.x (any minor version) or falls within 11.9.0 <= version < 11.10.0
  2. Confirm mapped drive usage
    Review the environment to determine if users have mapped network drives configured. Check if any network locations are mapped as drive letters (e.g., M:, Z:) that could contain sensitive data.
    Affected if Mapped drives are present in the environment and users can access files through them
  3. Verify web email client access
    Determine if users have access to web-based email clients (such as Outlook Web Access, Gmail, Yahoo Mail) from the protected endpoints.
    Affected if Web email clients are accessible from the endpoints where DLP is deployed
  4. Test upload behavior from mapped drives
    Attempt to upload a test file containing sensitive content (such as a fake credit card number or mock SSN) from a mapped drive to a web email client. Observe whether DLP blocks or detects the upload.
    Affected if The upload from the mapped drive to the web email client completes without DLP intervention, while the same upload from a local drive would be blocked

The environment is affected if DLP for Windows version 11.9.x is installed AND mapped drives are present AND users can access web email clients, as uploads from mapped drives to web email will bypass DLP protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.10.0 or later
Fixed in 11.10.0
Interim mitigation

Upgrade DLP for Windows to version 11.10.0 or later to restore proper scanning of mapped drive content during web email uploads.

Recommended fix High confidence

11.10.0 or later

  1. 1. Identify the current Data Loss Prevention (DLP) version installed on Windows systems by checking the Trellix agent or DLP console.
  2. 2. Confirm the installed version is >= 11.9.0 and < 11.10.0, which confirms exposure to CVE-2023-0400.
  3. 3. Plan the upgrade during a maintenance window, ensuring proper backups and rollback procedures are in place.
  4. 4. Upgrade DLP for Windows to version 11.10.0 or later using the Trellix upgrade mechanism (e.g., via ePolicy Orchestrator or manual installer).
  5. 5. After upgrade, verify the DLP version now shows 11.10.0 or higher.
  6. 6. Test the fix by attempting to upload sensitive data from a mapped drive to a web email client - it should now be correctly blocked.
Caveat Standard upgrade best practices apply - test in non-production environment first; review release notes for any configuration or compatibility changes in 11.10.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Loss Prevention Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0400 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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