CVE-2010-5191
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities on the Blue Coat ProxyAV appliance before 3.2.6.1 allow remote attackers to hijack the authentication of administrators for requests that (1) change a password, (2) modify a policy, or (3) restart the device.
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 confidenceMultiple cross-site request forgery (CSRF) vulnerabilities in Blue Coat ProxyAV appliance versions before 3.2.6.1 allow remote attackers to hijack administrator authentication for performing unauthorized password changes, policy modifications, and device restarts.
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<= 3.2.6= 3.1= 3.2all 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 appliance modelAccess the device console or web management interface and locate the system information or device status page to confirm the hardware is Blue Coat ProxyAV.Affected if The device model is Blue Coat ProxyAV or Bluecoat Avos.
-
Check the installed firmware versionVia the web management interface, navigate to the About or System Information page, or use the CLI command 'version' or 'show version' to retrieve the firmware version.Affected if The firmware version is any version of Bluecoat Avos <= 3.2.6, or specifically 3.1 or 3.2, or any version of Bluecoat Proxyav.
-
Confirm the web management interface is enabledVerify that the ProxyAV web administrative interface (typically HTTPS on port 8082 or 443) is accessible from the network. Check the device network settings or listening services.Affected if The web management interface is exposed and accessible.
-
Verify CSRF protection is absentAttempt to access a web administrative function (such as a settings page) and inspect whether the forms or requests include anti-CSRF tokens, unique session identifiers, or the Referer/Origin header validation.Affected if Administrative forms lack CSRF tokens or same-origin validation mechanisms.
The environment is affected if the device is a Blue Coat ProxyAV or Bluecoat Avos appliance running firmware version 3.2.6 or below with the web management interface accessible and no CSRF protection present.
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 ProxyAV firmware to version 3.2.6.1 or later, which contains the CSRF protection fixes.
3.2.6.1
- Upgrade Blue Coat ProxyAV appliance to version 3.2.6.1 or later
- After upgrade, verify the CSRF protections are functioning by reviewing administrator authentication mechanisms
- Confirm all administrator passwords are still as expected since the vulnerability could have allowed password changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5191 — 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-5191 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