CVE-2019-3639
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 · uneditedClickjack vulnerability in Adminstrator web console in McAfee Web Gateway (MWG) 7.8.2.x prior to 7.8.2.12 allows remote attackers to conduct clickjacking attacks via a crafted web page that contains an iframe via does not send an X-Frame-Options HTTP header.
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's Administrator web console fails to send the X-Frame-Options HTTP header, allowing the console interface to be embedded within an iframe on attacker-controlled web pages. This enables clickjacking attacks where users are tricked into performing unintended administrative actions through invisible or disguised UI elements.
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>= 7.8.2.0, < 7.8.2.12CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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 installed McAfee Web Gateway versionAccess the appliance CLI or admin interface and locate the version information, typically found in Help > About or via CLI command 'show version'Affected if Installed version is >= 7.8.2.0 and < 7.8.2.12
-
Confirm the admin console is accessibleNavigate to the Administrator web console URL (typically on port 443) and capture the HTTP response headers from the login page or any admin interface pageAffected if The admin console interface is reachable over HTTP/HTTPS
-
Inspect HTTP response for X-Frame-Options headerUsing browser developer tools (Network tab), curl, or a packet capture tool, examine the HTTP response headers from the admin console. Look specifically for 'X-Frame-Options' headerAffected if The X-Frame-Options header is absent from the HTTP responses
-
Verify header value is not DENY or SAMEORIGINIf X-Frame-Options exists, confirm it is set to either 'DENY' or 'SAMEORIGIN' - any other value or missing header indicates vulnerabilityAffected if X-Frame-Options is missing, set to a weak value like 'ALLOW', or not configured at all
The environment is affected if McAfee Web Gateway version is 7.8.2.0 through 7.8.2.11 AND the Administrator web console HTTP responses lack X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN headers.
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.8.2.12
Configure the MWG Administrator web console to include the X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN header in all HTTP responses, or implement Content-Security-Policy: frame-ancestors directive to restrict framing.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3639 — 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-3639 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