dbcve.org
Symantec ProxysgApplication · Broadcom

CVE-2021-30648

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-30
Fix available
A fix is available. Upgrade to 6.5.10.16 / 6.6.5.19 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
The Symantec Advanced Secure Gateway (ASG) and ProxySG web management consoles are susceptible to an authentication bypass vulnerability. An unauthenticated attacker can execute arbitrary CLI commands, view/modify the appliance configuration and policy, and shutdown/restart the appliance.

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

Authentication bypass vulnerability in Symantec ASG and ProxySG web management consoles allows unauthenticated attackers to execute arbitrary CLI commands, modify appliance configuration and policies, and shutdown/restart the appliance.

MitigationApply available patches from Broadcom for affected ASG and ProxySG versions; if no patch is available, restrict network access to management interfaces via firewall rules or VPN, and monitor for unauthorized access attempts.

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
Symantec ProxysgApplication
Affected:>= 6.5, < 6.5.10.16>= 6.6, < 6.6.5.19>= 6.7, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway S200 30 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway S200 40 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway S400 20 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway S400 30 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway S400 40 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway 500 10 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.3
Symantec Advanced Secure Gateway S500 20 FirmwareOperating system
Affected:>= 6.6, < 6.7.4.17>= 6.7.5.0, < 6.7.5.12>= 7.2, < 7.2.7.2>= 7.3, < 7.3.3.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
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 the product type
    Access the appliance CLI and run 'show version' or access the web management console and check the login page or about section to determine if the device is a ProxySG or Advanced Secure Gateway (ASG) model.
    Affected if The device is a Broadcom Symantec ProxySG or any ASG model (S200, S400, 500 series)
  2. Determine the installed firmware version
    Run 'show version' via CLI or check the web console's System > Maintenance > Version page to obtain the exact numeric firmware version.
    Affected if The version falls within any of these ranges: 6.5.x before 6.5.10.16, 6.6.x before 6.6.5.19, 6.7.x before 6.7.5.12 (or before 6.7.4.17 for ASG), 7.2.x before 7.2.7.2, or 7.3.x before 7.3.3.3
  3. Verify web management console accessibility
    Confirm whether the web management interface (HTTPS on ports 8082, 8443, or the administrative GUI) is reachable from network segments where untrusted users could access it.
    Affected if The web management console is exposed to untrusted networks without firewall restrictions
  4. Check for unauthorized CLI command execution indicators
    Review appliance logs in System > Logs > Management for entries showing CLI commands executed without prior authentication logs, or check for unexpected configuration changes in the policy traces.
    Affected if CLI commands appear in logs without corresponding authentication events, or unauthorized configuration changes are detected

The environment is affected if the device is a ProxySG or ASG appliance running a firmware version within the affected ranges AND the web management console is accessible to potential attackers.

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 6.5.10.16 / 6.6.5.19 / 6.7.4.17 or later
Fixed in 6.5.10.166.6.5.196.7.4.17
Interim mitigation

Apply available patches from Broadcom for affected ASG and ProxySG versions; if no patch is available, restrict network access to management interfaces via firewall rules or VPN, and monitor for unauthorized access attempts.

Recommended fix High confidence

Upgrade to ProxySG/ASG version 6.5.10.16 (or later 6.5.x), 6.6.5.19 (or later 6.6.x), 6.7.5.12 (or later 6.7.x), 7.2.7.2 (or later 7.2.x), or 7.3.3.3 (or later 7.3.x) depending on your current branch

  1. 1. Identify the currently installed version of the Symantec ProxySG or Advanced Secure Gateway appliance by accessing the management console or using the CLI command 'show version'
  2. 2. Navigate to the Broadcom Support portal at support.broadcom.com and locate the appropriate firmware/software update for your specific appliance model
  3. 3. Download the fixed version corresponding to your current branch: for 6.5.x branch download 6.5.10.16 or later; for 6.6.x branch download 6.6.5.19 or later; for 6.7.x branch download 6.7.5.12 or later; for 7.2.x branch download 7.2.7.2 or later; for 7.3.x branch download 7.3.3.3 or later
  4. 4. Review the upgrade documentation and release notes for any prerequisites or migration considerations
  5. 5. Backup the current appliance configuration using the management console or CLI command 'backup'
  6. 6. Apply the firmware/software update following the documented upgrade procedure for your appliance model
  7. 7. After upgrade completes, verify the new version is installed using 'show version'
  8. 8. Confirm the management console is accessible and the authentication mechanism is functioning properly
Caveat Review release notes for any policy or configuration syntax changes that may require adjustment after upgrading

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

Fix this in Symantec Proxysg Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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