dbcve.org
Web GatewayApplication · Mcafee

CVE-2022-1254

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-20
Fix available
A fix is available. Upgrade to 7.8.2.31 / 8.2.27 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A URL redirection vulnerability in Skyhigh SWG in main releases 10.x prior to 10.2.9, 9.x prior to 9.2.20, 8.x prior to 8.2.27, and 7.x prior to 7.8.2.31, and controlled release 11.x prior to 11.1.3 allows a remote attacker to redirect a user to a malicious website controlled by the attacker. This is possible because SWG incorrectly creates a HTTP redirect response when a user clicks a carefully constructed URL. Following the redirect response, the new request is still filtered by the SWG policy.

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 confidence

Skyhigh Secure Web Gateway contains an open redirect vulnerability where specially crafted URLs cause the SWG to incorrectly generate HTTP 302 redirect responses to attacker-controlled domains. Although redirected requests continue to be filtered by SWG policy, the initial redirect can socially engineer users who trust the original SWG-protected domain.

MitigationApply vendor-supplied patches: upgrade to 10.2.9+, 9.2.20+, 8.2.27+, 7.8.2.31+, or 11.1.3+ depending on your release branch.

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
Web GatewayApplication
Affected:>= 7.0.0, < 7.8.2.31>= 8.0.0, < 8.2.27>= 9.0.0, < 9.2.20>= 10.0.0, < 10.2.9>= 11.0.0, < 11.1.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

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

  1. Identify if McAfee or Skyhigh Web Gateway is running
    Check running processes for 'mwg' or 'webgateway' daemons, or scan network ports 8080, 8443 for the admin UI or proxy service
    Affected if The product is present and running as a proxy/gateway service
  2. Locate the product version via admin UI
    Access the web admin interface (typically https://<gateway-ip>:8443) and navigate to 'Help > About' or 'System > Status' to view the version number
    Affected if The displayed version falls within any of the affected ranges: 7.0.0-7.8.2.30, 8.0.0-8.2.26, 9.0.0-9.2.19, 10.0.0-10.2.8, or 11.0.0-11.1.2
  3. Locate the product version via command line
    On the appliance console, run: 'mwg-relog -v' or 'cat /opt/mwg/etc/version' (path may vary by installation)
    Affected if The returned version matches any of the affected ranges listed above
  4. Confirm redirect functionality is in use
    Verify the SWG is configured as a proxy or transparent proxy handling HTTP/HTTPS traffic - check proxy listening ports (typically 8080, 3128) and routing/iptables rules
    Affected if The gateway is actively proxying or redirecting user traffic (this is the default operational mode for SWG)

You are affected if McAfee Web Gateway or Skyhigh Secure Web Gateway is installed and the running version is lower than 7.8.2.31, 8.2.27, 9.2.20, 10.2.9, or 11.1.3 depending on your release branch.

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.

dbcve · scoped
Upgrade available Upgrade to 7.8.2.31 / 8.2.27 / 9.2.20 or later
Fixed in 7.8.2.318.2.279.2.20
Interim mitigation

Apply vendor-supplied patches: upgrade to 10.2.9+, 9.2.20+, 8.2.27+, 7.8.2.31+, or 11.1.3+ depending on your release branch.

Recommended fix High confidence

Upgrade to version 7.8.2.31 or later (7.x), 8.2.27 or later (8.x), 9.2.20 or later (9.x), or 10.2.9 or later (10.x)

  1. 1. Identify the current version of McAfee/Skyhigh Web Gateway installed in your environment
  2. 2. Determine which major version branch you are running (7.x, 8.x, 9.x, or 10.x)
  3. 3. Download the appropriate fixed version from the McAfee Knowledge Center (kc.mcafee.com) or your authorized download channel
  4. 4. Review the upgrade guide and release notes for your specific version path
  5. 5. Create a backup of the current configuration
  6. 6. Perform the upgrade during a planned maintenance window
  7. 7. Verify the upgrade was successful and the version number matches the fixed release
  8. 8. Test that the redirect functionality now properly validates URLs and does not allow arbitrary external redirects
Caveat Review release notes for your specific version upgrade path for any configuration or behavioral changes; standard upgrade precautions apply (backup configs, test in non-production first)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Web Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1254 — 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-2022-1254 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