CVE-2016-9100
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 · uneditedSymantec Advanced Secure Gateway (ASG) 6.6 prior to 6.6.5.13, ASG 6.7 prior to 6.7.3.1, ProxySG 6.5 prior to 6.5.10.6, ProxySG 6.6 prior to 6.6.5.13, and ProxySG 6.7 prior to 6.7.3.1 are susceptible to an information disclosure vulnerability. An attacker with local access to the client host of an authenticated administrator user can, under certain circumstances, obtain sensitive authentication credential information.
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 · moderate confidenceThis is a local information disclosure vulnerability in Symantec ASG and ProxySG products. An attacker with local access to the client host of an authenticated administrator user can, under certain circumstances, obtain sensitive authentication credential information. The vulnerability stems from improper handling of credentials in certain operations.
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.6, < 6.6.5.13>= 6.7, < 6.7.3.1>= 6.5, < 6.5.10.6>= 6.6, < 6.6.5.13>= 6.7, < 6.7.3.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionAccess the management console or CLI and retrieve the product name and version number. For ProxySG, this is typically visible on the login page or in the 'Statistics > General > System Information' page. For ASG, check 'Support > System Info' in the management interface.Affected if The product is Broadcom (formerly Symantec) ProxySG or ASG and the version falls within: ProxySG 6.5 through <6.5.10.6, 6.6 through <6.6.5.13, or 6.7 through <6.7.3.1; ASG 6.6 through <6.6.5.13 or 6.7 through <6.7.3.1
-
Verify local administrator access existsReview the list of configured administrative users or groups with local access privileges on the appliance. Check 'Configuration > Administrators' or 'Management > Users' in the management console.Affected if Local administrator accounts or authenticated administrator users have been configured, as the vulnerability requires an authenticated administrator user with local client host access
-
Review system logs for credential exposure indicatorsExamine appliance logs in 'Maintenance > Logs' or the local syslog for entries related to credential operations, password changes, or authentication events that may contain sensitive credential data in plaintext or encoded form.Affected if Logs contain entries with plaintext credentials, base64-encoded credentials, or other sensitive authentication information that should not be visible
-
Check for administrator workstation compromiseIf possible, review the client hosts used by administrators for local access. Examine browser credential storage, cached authentication data, or application logs on those workstations for leaked ProxySG or ASG credentials.Affected if Administrator workstation client hosts contain exposed or cached authentication credentials that could have been obtained through the vulnerable operations
A user is affected if they are running a vulnerable version of ProxySG (6.5-6.5.10.5, 6.6-6.6.5.12, or 6.7-6.7.3.0) or ASG (6.6-6.6.5.12 or 6.7-6.7.3.0) and have authenticated administrator accounts with local access, especially if credential exposure is found in logs or on admin workstations.
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.66.6.5.136.7.3.1
Apply vendor patches (ASG 6.6.5.13/6.7.3.1 or ProxySG 6.5.10.6/6.6.5.13/6.7.3.1 and later). Additionally, restrict local access to administrator workstations and ensure proper credential hygiene.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9100 — 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-2016-9100 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