CVE-2020-7306
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 · uneditedUnprotected Storage of Credentials vulnerability in McAfee Data Loss Prevention (DLP) for Mac prior to 11.5.2 allows local users to gain access to the ADRMS username and password via unprotected log files containing plain text
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 confidenceMcAfee Data Loss Prevention (DLP) for Mac prior to version 11.5.2 stores ADRMS username and password credentials in plain text within unprotected log files. Local users with standard system access can read these log files and obtain the stored credentials, leading to unauthorized access to the ADRMS service.
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.3.0, < 11.3.31>= 11.4.0, < 11.4.200>= 11.5.0, < 11.5.2CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/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.
-
Verify McAfee DLP for Mac is installedCheck for the presence of McAfee DLP on the system by looking for the installation directory or running: ls /Library/McAfee/ or which dlpAffected if McAfee DLP for Mac is not installed on the system
-
Determine the installed DLP versionCheck the installed version of McAfee DLP for Mac - this is typically available via the McAfee agent, in the application bundle, or via: defaults read /Library/McAfee/DLP/Info.plist CFBundleVersion 2>/dev/nullAffected if The installed version is 11.3.0 through 11.3.30, 11.4.0 through 11.4.199, or 11.5.0 through 11.5.1
-
Confirm ADRMS integration is configuredCheck if the Active Directory Rights Management Services (ADRMS) client is configured for use with DLP - look for ADRMS-related configuration files or registry equivalents in the DLP settings directoryAffected if ADRMS is not configured or used with DLP, the credential exposure does not apply
-
Inspect DLP log files for exposed credentialsExamine log files in the DLP logging directory (typically /Library/McAfee/DLP/logs/) for plaintext strings resembling usernames and passwords, particularly looking for patterns matching ADRMS credentialsAffected if Log files contain plaintext ADRMS usernames or passwords
A user is affected if McAfee DLP for Mac is installed with a version between 11.3.0 and 11.3.30, between 11.4.0 and 11.4.199, or between 11.5.0 and 11.5.1, and ADRMS is configured, with plain text credentials visible in DLP log files.
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 data11.3.3111.4.20011.5.2
Upgrade McAfee DLP for Mac to version 11.5.2 or later to remediate the vulnerability. As a precautionary measure, rotate the exposed ADRMS credentials since they may have been compromised.
- 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-2020-7306 — 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-2020-7306 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