CVE-2017-3899
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 · uneditedSQL injection vulnerability in Intel Security Advanced Threat Defense (ATD) Linux 3.6.0 and earlier allows remote authenticated users to obtain product information via a 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 · moderate confidenceSQL injection vulnerability in Intel Security Advanced Threat Defense (ATD) Linux version 3.6.0 and earlier allows remote authenticated users to inject malicious SQL commands through HTTP request parameters, enabling unauthorized access to product information stored in the backend database.
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.8.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/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.
-
Identify if Intel Security or McAfee Advanced Threat Defense is installedCheck for ATD installation directories (e.g., /opt/ATD, /opt/McAfee/ATD) or running processes: ps aux | grep -i 'atd' and look for service names like 'atd' or 'McAfeeATD'Affected if ATD software is found running on the system
-
Determine installed ATD versionCheck version file in installation directory (e.g., /opt/ATD/version or /opt/McAfee/ATD/version) or run: cat /opt/ATD/build.info 2>/dev/nullAffected if Installed version is 3.8.0 or lower (any version <= 3.8.0)
-
Verify HTTP management interface is accessibleTest connectivity to common ATD web ports (e.g., curl -k https://localhost:443 or check if port 443/8443 is listening: netstat -tlnp | grep -E ':(443|8443)'Affected if HTTP/HTTPS management interface is exposed and reachable
-
Confirm remote authentication is enabledCheck ATD configuration files for remote user authentication settings (e.g., /opt/ATD/conf/atd.conf or /opt/ATD/etc/config.xml) and verify authentication method allows remote usersAffected if Remote authenticated users can access the web interface (not limited to localhost only)
If ATD version is 3.8.0 or lower and the HTTP management interface accepts remote authenticated users, the environment is vulnerable to SQL injection via HTTP request parameters.
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 dataImplement parameterized queries or prepared statements for all database interactions, apply input validation and sanitization on HTTP request parameters, and consider upgrading to a patched version if available from Intel Security.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3899 — 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-2017-3899 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