dbcve.org
Secure Web GatewayApplication · Skyhighsecurity

CVE-2022-2310

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 8.2.28 / 9.2.23 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An authentication bypass vulnerability in Skyhigh SWG in main releases 10.x prior to 10.2.12, 9.x prior to 9.2.23, 8.x prior to 8.2.28, and controlled release 11.x prior to 11.2.1 allows a remote attacker to bypass authentication into the administration User Interface. This is possible because of SWG incorrectly whitelisting authentication bypass methods and using a weak crypto password. This can lead to the attacker logging into the SWG admin interface, without valid credentials, as the super user with complete control over the SWG.

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 SWG contains an authentication bypass vulnerability in its administration interface. The vulnerability exists because the software incorrectly whitelists authentication bypass methods and uses a weak cryptographic password, allowing a remote unauthenticated attacker to gain full administrative access as the super user.

MitigationUpgrade Skyhigh SWG to version 10.2.12, 9.2.23, 8.2.28, 11.2.1 or later per the affected release branch. If immediate patching is not possible, restrict administrative UI access to trusted IP addresses via network 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
Secure Web GatewayApplication
Affected:>= 8.0.0, < 8.2.28>= 9.0.0, < 9.2.23>= 10.0.0, < 10.2.12>= 11.0.0, < 11.2.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Skyhigh SWG version
    Check the installed version of Skyhigh Secure Web Gateway via the admin UI (typically displayed in System > Status or Help > About), or using CLI commands such as 'show version' or 'swg-version' if available
    Affected if Version falls within 8.0.0-8.2.27, 9.0.0-9.2.22, 10.0.0-10.2.11, or 11.0.0-11.0.x (any version below 8.2.28, 9.2.23, 10.2.12, or 11.2.1)
  2. Determine admin interface network exposure
    Review network configuration to determine if the Skyhigh SWG administration interface (typically ports 443 or 8443) is accessible from untrusted or external networks. Check firewall rules, ACLs, or reverse proxy settings that control access to the admin UI
    Affected if The admin interface is reachable from networks outside the trusted administrative zone, including the internet or untrusted internal segments

Environment is affected if running an affected version AND the administration interface is exposed to untrusted or anonymous network access.

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 8.2.28 / 9.2.23 / 10.2.12 or later
Fixed in 8.2.289.2.2310.2.12
Interim mitigation

Upgrade Skyhigh SWG to version 10.2.12, 9.2.23, 8.2.28, 11.2.1 or later per the affected release branch. If immediate patching is not possible, restrict administrative UI access to trusted IP addresses via network controls.

Recommended fix High confidence

Upgrade to 8.2.28+ (8.x branch), 9.2.23+ (9.x branch), 10.2.12+ (10.x branch), or 11.2.1+ (11.x branch) depending on your current major version

  1. 1. Identify the currently installed Secure Web Gateway version by checking the admin interface or system information.
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release: For 8.x versions, upgrade to 8.2.28 or later; For 9.x versions, upgrade to 9.2.23 or later; For 10.x versions, upgrade to 10.2.12 or later; For 11.x versions, upgrade to 11.2.1 or later.
  3. 3. Review the vendor's upgrade documentation and release notes for the target version.
  4. 4. Create a complete backup of the current SWG configuration.
  5. 5. Schedule a maintenance window as upgrades may require brief downtime.
  6. 6. Download the appropriate upgrade package from the vendor portal (kcm.trellix.com).
  7. 7. Apply the upgrade following the vendor's documented procedures.
  8. 8. After upgrade, verify the version number reflects the patched release.
Caveat Specific breaking changes are not detailed in the provided description; consult vendor release notes for your specific upgrade path

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

Fix this in Secure Web Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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 locally
dbcve dependency scanner

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