CVE-2019-3650
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 · uneditedInformation Disclosure vulnerability in McAfee Advanced Threat Defense (ATD prior to 4.8 allows remote authenticated attackers to gain access to the atduser credentials via carefully constructed GET request extracting insecurely information stored in the database.
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 prior to version 4.8 contains an information disclosure vulnerability where remote authenticated attackers can exploit a GET request parameter to extract atduser credentials from the database. The credentials are stored insecurely, allowing authenticated users to retrieve them through carefully crafted database queries.
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
- None
- Availability
- None
CVSS:3.1/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 the installed McAfee Advanced Threat Defense versionAccess the ATD administrative interface or check the system inventory for the ATD version number. This is typically visible in the product GUI under System > Information or in the about section.Affected if The installed version is any release prior to 4.8 (e.g., 4.7.x, 4.6.x, earlier versions).
-
Verify whether remote authentication is enabledReview the ATD authentication configuration settings in the administrative console. Check if local users or remote directory users can authenticate to the ATD interface.Affected if Remote authenticated access to the ATD interface is permitted to users who could potentially exploit the GET request parameter flaw.
-
Review access logs for suspicious GET requests targeting credential endpointsExamine the ATD server logs for unusual GET requests, particularly those containing database query patterns or requests to endpoints that could return user credential data.Affected if Any GET requests are observed that target credential retrieval endpoints or contain database query strings, especially from authenticated users.
-
Inspect database configuration and credential storage settingsReview the ATD database configuration files and storage mechanisms to confirm how atduser credentials are stored and whether they are encrypted or hashed.Affected if Credentials are found to be stored in an insecure manner (e.g., plaintext, weakly hashed, or reversible encoding).
A user is affected if McAfee Advanced Threat Defense is installed at any version prior to 4.8 and remote authenticated access is enabled, allowing attackers to exploit the GET request parameter to retrieve credentials from the database.
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 Advanced Threat Defense to version 4.8 or later, which addresses the insecure credential storage. If immediate upgrade is not possible, restrict access to authenticated users and monitor for suspicious GET requests targeting credential endpoints.
- 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-2019-3650 — 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-3650 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