CVE-2010-5189
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 · uneditedBlue Coat ProxySG before SGOS 4.3.4.1, 5.x before SGOS 5.4.5.1, 5.5 before SGOS 5.5.4.1, and 6.x before SGOS 6.1.1.1 allows remote authenticated users to execute arbitrary CLI commands by leveraging read-only administrator privileges and establishing an HTTPS session.
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 confidenceBlue Coat ProxySG contains a privilege escalation vulnerability where read-only administrators can execute arbitrary CLI commands by establishing an HTTPS session. The vulnerability exists in SGOS versions prior to 4.3.4.1, 5.x before 5.4.5.1, 5.5 before 5.5.4.1, and 6.x before 6.1.1.1. A read-only admin with network access can bypass intended restrictions to run commands at the full CLI level.
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<= 4.3.4= 3.2.6= 4.1.2.1= 4.2.1.2= 4.2.1.6= 4.2.2= 4.2.2.1= 4.2.2.2= 4.2.3= 4.2.3.4= 4.2.3.7= 4.2.3.12all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 SGOS versionLog into the ProxySG CLI and run 'show version' or view the version in the management web interfaceAffected if The version is earlier than 4.3.4.1, between 5.0.0 and 5.4.5.0, between 5.5.0 and 5.5.4.0, or earlier than 6.1.1.1 on the 6.x branch
-
Confirm read-only admin accounts existRun 'show admin-users' in the CLI or review admin account settings in the management interface to list all configured administrators and their privilege levelsAffected if Any read-only administrator accounts are configured on the device
-
Verify HTTPS management interface is enabledRun 'show management' in the CLI or check the management settings in the web interface to see if HTTPS access is permittedAffected if HTTPS management is enabled and allows administrative access
-
Check network exposure of management interfaceAttempt to reach the ProxySG management interface from your network segments or review firewall rules controlling access to port 443 on the deviceAffected if The HTTPS management port is reachable from networks that contain untrusted or unauthorized users
The environment is affected if the ProxySG runs a vulnerable SGOS version AND has read-only admin accounts configured with network access to the HTTPS management interface.
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.
dbcve · scopedUpgrade Blue Coat ProxySG to SGOS 4.3.4.1, 5.4.5.1, 5.5.4.1, 6.1.1.1 or later. If immediate patching is not possible, restrict read-only admin access to trusted personnel and monitor for unauthorized command execution.
SGOS 4.3.4.1 (for 4.x), SGOS 5.4.5.1 (for 5.x), SGOS 5.5.4.1 (for 5.5.x), or SGOS 6.1.1.1 (for 6.x)
- 1. Identify the current SGOS version running on the ProxySG device by accessing the Management Console or running 'show version' in the CLI.
- 2. Determine which upgrade path applies based on current version: if on 4.x branch, upgrade to SGOS 4.3.4.1; if on 5.x (before 5.4), upgrade to SGOS 5.4.5.1; if on 5.5.x, upgrade to SGOS 5.5.4.1; if on 6.x, upgrade to SGOS 6.1.1.1.
- 3. Download the appropriate SGOS firmware from the Blue Coat support portal (support.bluecoat.com).
- 4. Back up the current ProxySG configuration through the Management Console (Configuration > Archive > Backup).
- 5. Upload the new SGOS firmware through the Management Console (Maintenance > Firmware > Upload) or via CLI using 'firmware upload' command.
- 6. Reboot the ProxySG device to apply the new firmware.
- 7. After reboot, verify the new SGOS version is installed using 'show version' in the CLI.
- 8. Confirm the configuration was preserved and test that the vulnerability is mitigated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5189 — 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-2010-5189 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