CVE-2019-3660
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 Neutralization of HTTP requests in McAfee Advanced Threat Defense (ATD) prior to 4.8 allows remote authenticated attacker to execute commands on the server remotely via carefully constructed HTTP requests.
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 confidenceImproper neutralization of HTTP requests in McAfee Advanced Threat Defense (ATD) allows remote authenticated attackers to execute arbitrary operating system commands on the server by sending specially crafted HTTP requests. This is a command injection vulnerability in the web interface of the ATD product.
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.8CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if McAfee ATD is installedLook for the McAfee Advanced Threat Defense product on the system or in the software inventory. On the server, check common installation paths such as /opt/atd or C:\Program Files\McAfee\ATD, or check the system's installed software list.Affected if McAfee ATD software is present on the system
-
Determine the installed ATD versionAccess the ATD web interface and navigate to the About or System Information page, or check the version via the command line if available (such as running 'atd --version' or checking the installer). Compare the version number against the affected range.Affected if The installed version is lower than 4.8 (for example, 4.6, 4.7, or any 4.x version before 4.8)
-
Verify the ATD web interface is enabledCheck if the ATD web management interface (typically on port 443 or 8443) is accessible and running. This can be done by attempting to access the URL or checking if the web service process is running.Affected if The web interface is enabled and accessible, as this is the attack vector for command injection
-
Check network exposure of the ATD management interfaceReview firewall rules and network configuration to determine if the ATD web interface is exposed to network segments beyond trusted administrative networks. Use tools like netstat or port scans to identify listening ports.Affected if The management interface is reachable from untrusted networks or non-administrative IP addresses
A system is affected if McAfee Advanced Threat Defense is installed with a version lower than 4.8 and the web management interface is enabled and accessible.
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.8
Upgrade McAfee ATD to version 4.8 or later to obtain the vendor patch. If immediate patching is not feasible, implement network segmentation to restrict access to the ATD management interface to only trusted administrative IP addresses.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3660 — 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-2019-3660 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