CVE-2014-2033
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 caching feature in SGOS in Blue Coat ProxySG 5.5 through 5.5.11.3, 6.1 through 6.1.6.3, 6.2 through 6.2.15.3, 6.4 through 6.4.6.1, and 6.3 and 6.5 before 6.5.4 allows remote authenticated users to bypass intended access restrictions during a time window after account deletion or modification by leveraging knowledge of previously valid credentials.
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 confidenceThe SGOS caching feature in Blue Coat ProxySG maintains authentication tokens in cache even after account deletion or modification. This allows previously authenticated users to continue accessing the proxy during a time window before cache expiration, bypassing updated access restrictions.
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>= 5.5, <= 5.5.11.3>= 6.1, <= 6.1.6.3>= 6.2, <= 6.2.15.3>= 6.4, <= 6.4.6.1>= 6.5, < 6.5.4= 6.3CVSS 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/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 Blue Coat ProxySG installationLocate the ProxySG device or virtual appliance in your environment and confirm it is running SGOS.Affected if Blue Coat ProxySG is not present in the environment.
-
Determine installed SGOS versionAccess the ProxySG management console or CLI and run 'show version' to obtain the SGOS version number.Affected if The version falls within any of these ranges: 5.5 through 5.5.11.3, 6.1 through 6.1.6.3, 6.2 through 6.2.15.3, 6.4 through 6.4.6.1, 6.5.0 through 6.5.3, or exactly 6.3.x.
-
Verify authentication caching is enabledIn the ProxySG management interface, navigate to Configuration > Authentication > General or use CLI 'show authentication' to confirm credential caching is active.Affected if Authentication caching is enabled and the version is affected.
-
Check credential cache TTL settingIn the management console, locate the authentication cache time-to-live setting under Authentication > General or Cache Settings. Note the current TTL value.Affected if A non-zero TTL is configured, allowing cached tokens to persist after account modification.
The environment is affected if a Blue Coat ProxySG is running with an SGOS version in the affected ranges and authentication caching is enabled with a non-zero TTL, allowing deleted or modified user accounts to retain access via cached credentials.
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.4
Upgrade to Blue Coat ProxySG version 6.5.4 or later (6.3.x/6.5.x branches), or the patched versions for other branches (5.5.11.4, 6.1.6.4, 6.2.15.4, 6.4.6.2). As a compensating control, reduce credential cache TTL if supported.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2033 — 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-2014-2033 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