dbcve.org
Advanced Secure GatewayApplication · Broadcom

CVE-2018-18370

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-30
Fix available
A fix is available. Upgrade to 6.5.10.15 / 6.7.4.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 ASG/ProxySG FTP proxy WebFTP mode allows intercepting FTP connections where a user accesses an FTP server via a ftp:// URL in a web browser. A stored cross-site scripting (XSS) vulnerability in the WebFTP mode allows a remote attacker to inject malicious JavaScript code in ASG/ProxySG's web listing of a remote FTP server. Exploiting the vulnerability requires the attacker to be able to upload crafted files to the remote FTP server. Affected versions: ASG 6.6 and 6.7 prior to 6.7.4.2; ProxySG 6.5 prior to 6.5.10.15, 6.6, and 6.7 prior to 6.7.4.2.

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

A stored cross-site scripting (XSS) vulnerability exists in the WebFTP mode of Blue Coat ASG and ProxySG FTP proxy appliances. Attackers can upload files with embedded malicious JavaScript to a remote FTP server. When users access this FTP server through the proxy's WebFTP interface using a web browser, the malicious script executes in the user's browser context, potentially stealing session cookies or performing actions on behalf of the user.

MitigationApply vendor patches: upgrade ASG to version 6.7.4.2 or later, or ProxySG to 6.5.10.15/6.7.4.2 or later. As an interim measure, disable WebFTP mode or restrict FTP access to trusted servers.

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:>= 6.7, < 6.7.4.2= 6.6
Symantec ProxysgApplication
Affected:>= 6.5, < 6.5.10.15>= 6.7, < 6.7.4.2= 6.6

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

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the appliance product and firmware version
    Access the management console or use the CLI command to display the system version. For ProxySG, this is typically shown on the main dashboard or via 'show version' command. For ASG, check the system information page in the management interface.
    Affected if The installed version falls within any of these ranges: ASG 6.6, or ASG >= 6.7 to < 6.7.4.2; ProxySG 6.6, ProxySG >= 6.5 to < 6.5.10.15, or ProxySG >= 6.7 to < 6.7.4.2
  2. Determine if WebFTP mode is enabled
    Check the proxy configuration settings for WebFTP functionality. In the management console, navigate to the FTP proxy settings or WebFTP configuration section and verify the current status.
    Affected if WebFTP mode is currently enabled and accessible to users
  3. Verify FTP proxy service is configured and active
    Confirm that the FTP proxy service is running and accepting connections. Check the proxy services list or FTP proxy policy configuration in the management console.
    Affected if FTP proxy service is active and users can connect to external FTP servers through it
  4. Confirm users can access WebFTP through browsers
    Test whether the WebFTP interface is accessible by attempting to connect to an FTP server via the proxy's web interface. Check the proxy policies or access control lists that permit WebFTP traffic.
    Affected if WebFTP is accessible via browser and users can browse FTP servers through the proxy

You are affected if your appliance runs any version listed in the affected ranges AND WebFTP mode is enabled and accessible to users.

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.

From vendor data
Upgrade available Upgrade to 6.5.10.15 / 6.7.4.2 or later
Fixed in 6.5.10.156.7.4.2
Interim mitigation

Apply vendor patches: upgrade ASG to version 6.7.4.2 or later, or ProxySG to 6.5.10.15/6.7.4.2 or later. As an interim measure, disable WebFTP mode or restrict FTP access to trusted servers.

Fix this in Advanced Secure Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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