CVE-2015-3028
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 · uneditedMcAfee Advanced Threat Defense (MATD) before 3.4.4.63 allows remote authenticated users to bypass intended restrictions and change or update configuration settings via crafted parameters.
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 confidenceMcAfee Advanced Threat Defense (MATD) versions before 3.4.4.63 contain an authorization bypass vulnerability where remote authenticated users can bypass intended restrictions and modify configuration settings through crafted parameters. This allows privileged users to change system configurations beyond their intended authorization level.
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<= 3.4.4.14CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/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 if McAfee Advanced Threat Defense is installedLocate the MATD installation directory or check system services for 'McAfee ATD' or 'McAfee Advanced Threat Defense' service entryAffected if The product is present on the system
-
Determine the installed MATD versionAccess the MATD web interface or administrative console, navigate to the About or System Information section to view the exact version number (e.g., 3.4.4.x)Affected if The installed version is less than 3.4.4.63 (e.g., 3.4.4.14, 3.4.0, 3.3.x, etc.)
-
Verify if remote administrative access is enabledCheck MATD network settings to confirm whether remote administrative interface (web GUI or API) is accessible from network locationsAffected if Remote administrative access is enabled and the system is network-reachable
-
Check for user accounts with elevated privilegesReview MATD user management console to list all configured users and their assigned roles (Administrator, Analyst, Operator, etc.)Affected if Multiple user roles exist beyond a single administrator account, indicating the authorization bypass could be exploited
-
Audit configuration change logs for unauthorized modificationsExamine MATD audit logs or configuration history for recent changes made by users that may exceed their assigned authorization levelAffected if Configuration changes appear that were made by users whose roles should not permit such modifications
The environment is affected if McAfee ATD is installed with a version less than 3.4.4.63 and remote authenticated users can access the administrative interface.
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 dataUpgrade McAfee Advanced Threat Defense to version 3.4.4.63 or later. Until upgrade is possible, limit administrative access to only highly trusted personnel and monitor configuration change logs for unauthorized modifications.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3028 — 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-2015-3028 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