dbcve.org
Secure Web GatewayApplication · Skyhighsecurity

CVE-2023-4400

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to 10.2.25 / 11.2.14 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A password management vulnerability in Skyhigh Secure Web Gateway (SWG) in main releases 11.x prior to 11.2.14, 10.x prior to 10.2.25 and controlled release 12.x prior to 12.2.1, allows some authentication information stored in configuration files to be extracted through SWG REST API. This was possible due to SWG storing the password in plain text in some configuration files.

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 stores certain authentication credentials in plain text within configuration files. These credentials can be extracted by authenticated users through the SWG REST API, allowing unauthorized access to the stored authentication information.

MitigationApply the vendor-supplied patches: upgrade to version 11.2.14 (or later), 10.2.25 (or later), or 12.2.1 (or later) to remediate the plain-text password storage vulnerability.

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:>= 10.0.0, < 10.2.25>= 11.0.0, < 11.2.14>= 12.0.0, < 12.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Verify Skyhigh SWG version
    Access the SWG admin console or use the command line interface to retrieve the installed version. Typically found in System > Status or via CLI command 'show version' or similar.
    Affected if The installed version falls within 10.0.0 to 10.2.24, 11.0.0 to 11.2.13, or 12.0.0 to 12.2.0.
  2. Locate configuration files with stored credentials
    Access the configuration directory (commonly /opt/mwg/ or similar installation paths) and inspect XML or configuration files for credential storage entries. Look for password or credential-related configuration sections.
    Affected if Plain text passwords are present in any configuration or credential storage files.
  3. Verify REST API accessibility
    As an authenticated user with standard API permissions, attempt to query the REST API endpoints that return configuration or credential data. Check if unauthenticated or lower-privilege users can retrieve credential information.
    Affected if Authenticated users can extract stored credentials through the REST API without elevated privileges.
  4. Inspect credential storage mechanism
    Review the SWG configuration backup files or export the configuration and search for password fields. Compare encrypted versus plaintext storage methods.
    Affected if Passwords are stored in cleartext format rather than being hashed or encrypted.

You are affected if your Skyhigh Secure Web Gateway version is below 10.2.25, 11.2.14, or 12.2.1 AND plain text credentials exist in configuration files that are accessible via the REST API.

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 10.2.25 / 11.2.14 / 12.2.1 or later
Fixed in 10.2.2511.2.1412.2.1
Interim mitigation

Apply the vendor-supplied patches: upgrade to version 11.2.14 (or later), 10.2.25 (or later), or 12.2.1 (or later) to remediate the plain-text password storage vulnerability.

Recommended fix High confidence

Upgrade to 10.2.25 (10.x branch), 11.2.14 (11.x branch), or 12.2.1 (12.x branch) depending on your current major version

  1. 1. Identify the currently installed SWG version by checking the system administration console or using the CLI command 'swgversion'
  2. 2. If running version 10.0.0 through 10.2.24, plan upgrade to version 10.2.25 or later
  3. 3. If running version 11.0.0 through 11.2.13, plan upgrade to version 11.2.14 or later
  4. 4. If running version 12.0.0 through 12.2.0, plan upgrade to version 12.2.1 or later
  5. 5. Before upgrading, review the release notes for the target version to understand any required pre-upgrade steps or migration procedures
  6. 6. Perform a full backup of the current SWG configuration
  7. 7. Execute the upgrade following the vendor's documented upgrade procedure
  8. 8. After upgrade, verify the REST API no longer exposes plain-text passwords in configuration file responses
Caveat Review release notes for the target version; major version upgrades may include breaking changes requiring configuration adjustments or downtime

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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