CVE-2023-0214
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 · uneditedA cross-site scripting vulnerability in Skyhigh SWG in main releases 11.x prior to 11.2.6, 10.x prior to 10.2.17, and controlled release 12.x prior to 12.0.1 allows a remote attacker to craft SWG-specific internal requests with URL paths to any third-party website, causing arbitrary content to be injected into the response when accessed through 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 confidenceCross-site scripting vulnerability in Skyhigh Secure Web Gateway allows remote attackers to inject arbitrary content into responses by crafting SWG-specific internal requests with URL paths to third-party websites. When these requests are processed through the SWG proxy, malicious content can be injected into the response, potentially affecting users accessing those destinations through the gateway.
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>= 10.0.0, < 10.2.17>= 11.0.0, < 11.2.6= 12.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Skyhigh SWG versionLog into the SWG management console or use the command line interface (e.g., 'swg_version' or check system information in the admin UI) to retrieve the exact version numberAffected if The installed version falls within any of these ranges: >= 10.0.0 and < 10.2.17, >= 11.0.0 and < 11.2.6, or exactly 12.0.0
-
Verify the SWG proxy service is activeCheck if the Secure Web Gateway proxy service is running, typically via the management console status page or CLI command such as 'service swg-proxy status' or similarAffected if The proxy service is enabled and processing traffic, which is required for the vulnerability to be exploitable
-
Confirm proxy configuration allows external URL processingReview the proxy policy settings in the SWG management console under Proxy Settings or Policy Configuration to verify if forwarding of requests to third-party websites is permittedAffected if The proxy is configured to forward or process requests to external third-party URLs, which enables the attack vector described in the CVE
A user is affected if their Skyhigh Secure Web Gateway version is 10.0.0 through 10.2.16, 11.0.0 through 11.2.5, or exactly 12.0.0, and the SWG proxy service is actively processing traffic to external URLs.
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.
dbcve · scoped10.2.1711.2.6
Upgrade Skyhigh SWG to version 11.2.6, 10.2.17, or 12.0.1 or later to apply the security patch.
Skyhigh SWG 10.2.17, 11.2.6, or 12.0.1 (depending on your major version branch)
- Identify the current Skyhigh Secure Web Gateway version in use via the management console or CLI
- Download the appropriate fixed version from the official Skyhigh/Trellix support portal (10.2.17+, 11.2.6+, or 12.0.1+)
- Review release notes for upgrade prerequisites and any prerequisites
- Create a backup of the current configuration
- Schedule a maintenance window as upgrades may require service interruption
- Perform the upgrade following the official migration/upgrade guide
- Verify the upgrade was successful by checking the version in the management console
- Validate that the XSS vulnerability is remediated by testing the previously vulnerable URL paths
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0214 — 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-2023-0214 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