CVE-2019-3644
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 Web Gateway (MWG) earlier than 7.8.2.13 is vulnerable to a remote attacker exploiting CVE-2019-9517, potentially leading to a denial of service. This affects the scanning proxies.
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 confidenceMcAfee Web Gateway versions prior to 7.8.2.13 contain a vulnerability that allows remote attackers to exploit CVE-2019-9517 (an HTTP/2 ping flood DoS vulnerability) through the scanning proxies, potentially causing denial of service.
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= 1.0.0= 1.1.0= 2.0= 2.0.1= 2.1= 2.2= 2.3= 2.4= 4.0= 4.2= 4.4= 4.6= 10.2.0= 10.3.4= 10.4.0= 11.0.0= 11.1.0= 11.1.1= 11.1.2= 11.1.3= 11.2.0>= 7.7.2.0, < 7.7.2.24>= 7.8.2, < 7.8.2.13>= 8.0.0, < 8.2.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed McAfee productReview installed software or check the product name through the McAfee agent or system inventoryAffected if The product is one of: McAfee Active Response, McAfee Advanced Threat Defense, McAfee Enterprise Security Manager, or McAfee Web Gateway
-
Check McAfee Web Gateway versionAccess the Web Gateway admin console or run command: grep -i version /opt/mwg/bin/mwg-version 2>/dev/null or check the About section in the admin UIAffected if Version is 7.7.2.0 through 7.7.2.23, 7.8.2 through 7.8.2.12, or 8.0.0 through 8.1.x (below 8.2.0)
-
Check McAfee Active Response versionUse the ePO console or run: /opt/MAR/mar --version or check Add/Remove Programs for version informationAffected if Version equals 1.0.0, 1.1.0, 2.0, 2.0.1, 2.1, 2.2, 2.3, or 2.4
-
Check McAfee Advanced Threat Defense versionAccess the ATD admin interface or check system inventory for version numberAffected if Version equals 4.0, 4.2, 4.4, or 4.6
-
Check McAfee Enterprise Security Manager versionAccess ESM console or check installation directory for version infoAffected if Version equals 10.2.0, 10.3.4, 10.4.0, 11.0.0, 11.1.0, 11.1.1, 11.1.2, 11.1.3, or 11.2.0
You are affected if you run McAfee Web Gateway below 7.8.2.13, or any of the other listed product versions, and the HTTP/2 scanning proxy feature is enabled.
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 data7.7.2.247.8.2.138.2.0
Upgrade McAfee Web Gateway to version 7.8.2.13 or later to patch the vulnerability.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3644 — 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-3644 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