dbcve.org
Mcafee Web GatewayApplication · Mcafee

CVE-2019-3581

HIGH · 7.5 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to 7.8.2.5 / 8.0.2.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Improper input validation in the proxy component of McAfee Web Gateway 7.8.2.0 and later allows remote attackers to cause a denial of service 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 confidence

McAfee Web Gateway's proxy component has improper input validation that allows remote attackers to cause denial of service by sending crafted HTTP request parameters. The vulnerability affects version 7.8.2.0 and later.

MitigationApply vendor-supplied patches for McAfee Web Gateway and review proxy configuration for input validation controls.

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
Mcafee Web GatewayApplication
Affected:>= 7.8.2.0, < 7.8.2.5>= 8.0.0.0, < 8.0.2.0

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify McAfee Web Gateway version
    Locate the installed version of McAfee Web Gateway in the system management console, about page, or version command output
    Affected if Version is 7.8.2.0 through 7.8.2.4, or 8.0.0.0 through 8.0.1.x
  2. Confirm proxy component is active
    Verify that the proxy service or module is enabled and running on the McAfee Web Gateway
    Affected if Proxy component is enabled and processing HTTP requests
  3. Check HTTP request handling
    Review proxy configuration for input validation settings related to HTTP request parameters
    Affected if Input validation for HTTP request parameters is not explicitly configured or hardened
  4. Review proxy access logs
    Examine proxy logs for unusual denial of service patterns or malformed HTTP request parameter errors
    Affected if Logs show malformed parameter errors or service degradation tied to crafted requests

Your environment is affected if McAfee Web Gateway version falls within 7.8.2.0-7.8.2.4 or 8.0.0.0-8.0.1.x AND the proxy component is enabled and processing HTTP traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 7.8.2.5 / 8.0.2.0 or later
Fixed in 7.8.2.58.0.2.0
Interim mitigation

Apply vendor-supplied patches for McAfee Web Gateway and review proxy configuration for input validation controls.

Fix this in Mcafee Web Gateway Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3581 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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