CVE-2016-10258
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 · uneditedUnrestricted file upload vulnerability in the Symantec Advanced Secure Gateway (ASG) and ProxySG management consoles. A malicious appliance administrator can upload arbitrary malicious files to the management console and trick another administrator user into downloading and executing malicious code.
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 confidenceUnrestricted file upload vulnerability in Symantec ASG and ProxySG management consoles allows a malicious appliance administrator to upload arbitrary files. The attacker then social engineers another administrator into downloading and executing these malicious files, potentially leading to code execution on the appliance or connected systems.
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.14>= 6.7, < 6.7.3.1>= 6.5, < 6.5.10.8>= 6.6, < 6.6.5.14>= 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:R/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 the installed productLog into the appliance CLI or management console and run 'show version' or check the product name in the management interface headerAffected if The product is Broadcom Advanced Secure Gateway (ASG) or Broadcom Symantec ProxySG
-
Determine the installed version numberRun 'show version' command via CLI or check the version displayed in the management console footer/headerAffected if The version falls outside these safe versions: ASG 6.6.5.14+, 6.7.3.1+; ProxySG 6.5.10.8+, 6.6.5.14+, 6.7.3.1+
-
Verify management console is enabledCheck if the HTTPS management interface (typically port 8082) is accessible and enabled via 'show management' CLI commandAffected if The management console is accessible and the appliance has administrative users configured
-
Confirm administrative user access existsList administrative accounts via 'show administration' or check user configuration in the management console under 'Administration > Administrators'Affected if One or more administrator accounts are configured, providing the attacker vector described in the CVE
A user is affected if they are running ASG or ProxySG versions within the vulnerable ranges AND the management console is accessible with administrative accounts configured.
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.86.6.5.146.7.3.1
Restrict administrative access to trusted personnel, implement strict file upload validation and whitelisting in the management console, and apply vendor patches if available. Additionally, enforce least-privilege admin accounts and monitor for anomalous upload activity.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10258 — 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-10258 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