dbcve.org
Advanced Secure GatewayApplication · Broadcom

CVE-2023-23954

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-01
Fix available
A fix is available. Upgrade to 3.1.6.0 / 7.3.13.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Advanced Secure Gateway and Content Analysis, prior to 7.3.13.1 / 3.1.6.0, may be susceptible to a Stored Cross-Site Scripting vulnerability.

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

Stored Cross-Site Scripting (XSS) vulnerability in Sophos Advanced Secure Gateway and Content Analysis allows attackers to inject malicious scripts into the web interface that persist and execute when other users view the affected content.

MitigationUpgrade to version 7.3.13.1 (for ASG) or 3.1.6.0 (for Content Analysis) or later to resolve the 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
Advanced Secure GatewayApplication
Affected:< 7.3.13.1
Content AnalysisApplication
Affected:< 3.1.6.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 which product is deployed
    Determine if Broadcom Advanced Secure Gateway, Broadcom Content Analysis, or both are installed in your environment. Check the product name displayed in the web management interface or the system hostname/identifier.
    Affected if Either product is present and the version is below the fixed releases
  2. Check Advanced Secure Gateway version
    Log into the ASG web management console and navigate to the version or system information page, typically found under Administration > System > Version or similar. Record the displayed version number.
    Affected if The installed version is below 7.3.13.1
  3. Check Content Analysis version
    Log into the Content Analysis web management console and navigate to the version or system information page, typically found under Administration > System > Version or similar. Record the displayed version number.
    Affected if The installed version is below 3.1.6.0
  4. Confirm web interface is accessible
    Verify that the web management interface is reachable and operational by attempting to access the login page over HTTPS on the standard management port (typically 443 or 9443).
    Affected if The web interface is accessible AND the product version is below the fixed release

You are affected if either Broadcom Advanced Secure Gateway below version 7.3.13.1 or Broadcom Content Analysis below version 3.1.6.0 is installed and the web management interface is accessible.

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 3.1.6.0 / 7.3.13.1 or later
Fixed in 3.1.6.07.3.13.1
Interim mitigation

Upgrade to version 7.3.13.1 (for ASG) or 3.1.6.0 (for Content Analysis) or later to resolve the vulnerability.

Recommended fix High confidence

Advanced Secure Gateway: 7.3.13.1 or later; Content Analysis: 3.1.6.0 or later

  1. 1. Identify which product(s) are deployed: Advanced Secure Gateway (ASG), Content Analysis, or both
  2. 2. Determine current version by accessing the admin console or using CLI commands (e.g., 'version' command)
  3. 3. Create a full backup of the current configuration before proceeding with the upgrade
  4. 4. Download the fixed release from Broadcom support portal (support.broadcom.com) - ensure you download version 7.3.13.1 or later for ASG, or version 3.1.6.0 or later for Content Analysis
  5. 5. Review the upgrade documentation and release notes for any specific upgrade prerequisites or procedures
  6. 6. Apply the upgrade following Broadcom's documented upgrade procedure for your deployment model
  7. 7. After upgrade, verify the new version is running and confirm the vulnerability is resolved
  8. 8. Test critical functionality to ensure the upgrade did not introduce issues

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

Fix this in Advanced Secure Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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