CVE-2018-18371
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 · uneditedThe 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. An information disclosure vulnerability in the WebFTP mode allows a malicious user to obtain plaintext authentication credentials for a remote FTP server from the ASG/ProxySG's web listing of the 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 confidenceThis is an information disclosure vulnerability in the ASG/ProxySG FTP proxy WebFTP mode. When users access FTP servers via ftp:// URLs in web browsers through the proxy, the WebFTP feature displays a web listing that exposes plaintext authentication credentials for the remote FTP server. A malicious user who can access this web listing can retrieve these credentials.
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>= 6.7, < 6.7.4.2= 6.6>= 6.5, < 6.5.10.15>= 6.7, < 6.7.4.2= 6.6CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionAccess the appliance management console or CLI and locate the software version information. For CLI, this is typically shown at login or via a 'show version' or 'version' command.Affected if The installed version matches one of the affected ranges: ASG 6.6 or >= 6.7 to < 6.7.4.2; ProxySG 6.6 or >= 6.7 to < 6.7.4.2, or >= 6.5 to < 6.5.10.15.
-
Confirm product typeDetermine whether the device is an ASG (Advanced Secure Gateway) or ProxySG appliance. This is visible in the management interface or CLI startup banner.Affected if The product is either Broadcom Advanced Secure Gateway or Broadcom Symantec ProxySG.
-
Check if WebFTP mode is enabledAccess the proxy configuration settings. In the management console, navigate to the FTP proxy settings or WebFTP configuration area. Alternatively, use the CLI to view FTP proxy policy configuration.Affected if WebFTP mode is currently enabled, allowing web-based FTP directory listings through the proxy.
-
Verify FTP proxy policy existsReview the proxy policy configuration to confirm there is an active FTP proxy policy handling ftp:// URL requests.Affected if An FTP proxy policy exists that routes ftp:// URL traffic through the WebFTP feature.
The environment is affected if the installed ASG or ProxySG version falls within the vulnerable ranges AND WebFTP mode is enabled to handle FTP traffic through the proxy.
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.
From vendor data6.5.10.156.7.4.2
Upgrade ASG to version 6.7.4.2 or later, and upgrade ProxySG to 6.5.10.15 or later (or 6.7.4.2 or later for versions 6.6 and 6.7). As a temporary workaround, disable the WebFTP mode if not required.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18371 — 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-2018-18371 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