CVE-2020-7262
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 · uneditedImproper Access Control vulnerability in McAfee Advanced Threat Defense (ATD) prior to 4.10.0 allows local users to view sensitive files via a carefully crafted HTTP request parameter.
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 Advanced Threat Defense (ATD) versions prior to 4.10.0 contain an Improper Access Control vulnerability where local users can view sensitive files by manipulating HTTP request parameters. The vulnerability allows authenticated local users to bypass intended access restrictions and access files outside their authorized scope through specially crafted HTTP requests.
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< 4.10.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Determine the installed McAfee ATD versionAccess the ATD management console and navigate to System > About, or use the command line interface (CLI) command 'show system-info' to retrieve the firmware/software versionAffected if The installed version is any release prior to 4.10.0 (for example, 4.8.x, 4.9.x)
-
Verify local user account existenceAccess ATD user management via the management console under User Administration or use CLI command 'show user' to list all configured local usersAffected if Any local user accounts are present on the system (the vulnerability allows authenticated local users to bypass restrictions)
-
Review HTTP access logs for anomalous requestsExamine ATD web server access logs, typically found in /var/log/httpd/ or through the management console log viewer, focusing on requests that contain directory traversal patterns (such as '../') or unusual file path parametersAffected if Logs show requests from local user accounts accessing file paths outside the expected document root or configuration directories
-
Check for unauthorized file access attemptsSearch logs for HTTP GET or POST requests to sensitive system files, configuration files, or paths outside the normal ATD web application directory structureAffected if Evidence exists of requests successfully retrieving files that should not be accessible to the requesting user scope
Your environment is affected if McAfee ATD is installed at a version prior to 4.10.0 and local user authentication is enabled, regardless of whether exploitation is observed in logs.
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 data4.10.0
Upgrade McAfee Advanced Threat Defense to version 4.10.0 or later to obtain the patch for this vulnerability. As a compensating control, limit local user privileges and monitor for anomalous HTTP requests to sensitive file locations.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7262 — 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-7262 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