dbcve.org
Mcafee AgentApplication · Mcafee

CVE-2017-3896

MEDIUM · 5.9 CVSS v3.0 Published 2017-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Unvalidated parameter vulnerability in the remote log viewing capability in Intel Security McAfee Agent 5.0.x versions prior to 5.0.4.449 allows remote attackers to pass unexpected input parameters via a URL that was not completely validated.

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 confidence

Unvalidated parameter vulnerability in McAfee Agent 5.0.x remote log viewing capability allows remote attackers to inject unexpected input via unvalidated URL parameters, potentially leading to unexpected behavior.

MitigationUpdate McAfee Agent to version 5.0.4.449 or later which includes proper URL parameter validation in the remote log viewing component.

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
Mcafee AgentApplication
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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 McAfee Agent version
    Open Windows Registry and navigate to HKLM\SOFTWARE\McAfee\Agent\, or run 'C:\Program Files\McAfee\Common Framework\cmdagent -p' from command prompt to retrieve the installed agent version
    Affected if The installed version is exactly 5.0.0, 5.0.1, 5.0.2, 5.0.3, or 5.0.4
  2. Confirm remote log viewing capability is accessible
    Check if the McAfee Agent web server component is running by examining the ' Framework Service' in Windows Services or reviewing network listening ports (default HTTP port 8081) via 'netstat -an | findstr 8081'
    Affected if The agent's HTTP/HTTPS listener for remote access is active and reachable on the network
  3. Verify remote log viewing is enabled
    Check McAfee Agent policy settings in ePO console under 'Agent' > 'General' > 'Remote Logging', or inspect registry key HKLM\SOFTWARE\McAfee\Agent\RemoteLogView for a value of 1 (enabled)
    Affected if Remote log viewing capability is explicitly enabled in the agent configuration or policy

You are affected if McAfee Agent version is exactly 5.0.0 through 5.0.4 AND the remote log viewing HTTP service is enabled and accessible on your network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update McAfee Agent to version 5.0.4.449 or later which includes proper URL parameter validation in the remote log viewing component.

Fix this in Mcafee Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3896 — 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-2017-3896 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