Secure DesktopApplication · Cisco
CVE-2015-0691
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 · uneditedA certain Cisco JAR file, as distributed in Cache Cleaner in Cisco Secure Desktop (CSD), allows remote attackers to execute arbitrary commands via a crafted web site, aka Bug ID CSCup83001.
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 confidenceA JAR file distributed with Cisco Secure Desktop's Cache Cleaner component contains a command injection vulnerability. Remote attackers can exploit this by tricking users into visiting a crafted malicious website, which triggers the vulnerable JAR to execute arbitrary commands on the affected system with elevated privileges.
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
Secure DesktopApplication
= 3.0_base= 3.1.0.31= 3.1.1= 3.1.1.45= 3.1_base= 3.2.0.136= 3.2.1.103= 3.2.1.126= 3.2_base= 3.3.0.118= 3.3.0.151= 3.3_baseCVSS 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.
-
Determine if Cisco Secure Desktop is installedCheck for Cisco Secure Desktop installation directories or installed programs list. Common locations include C:\Program Files\Cisco\Cisco Secure Desktop or C:\Program Files (x86)\Cisco\Cisco Secure Desktop on Windows, or /opt/cisco/secure-desktop on Linux/Unix systems.Affected if Cisco Secure Desktop is present on the system
-
Identify the installed version of Cisco Secure DesktopLocate the version information in the installation directory, or check the program's properties/details in the Windows Add/Remove Programs list, or look for version files such as version.txt, csd_version, or similar within the Cisco Secure Desktop installation directory.Affected if The installed version matches one of the affected versions: 3.0_base, 3.1.0.31, 3.1.1, 3.1.1.45, 3.1_base, 3.2.0.136, 3.2.1.103, 3.2.1.126, 3.2_base, 3.3.0.118, 3.3.0.151, or 3.3_base
-
Verify if the Cache Cleaner component is present and enabledLocate the Cache Cleaner JAR file within the Cisco Secure Desktop installation directory (commonly in a subdirectory named cachecleaner, lib, or similar). Check for files with .jar extension related to Cache Cleaner. On Windows, also check for the Cache Cleaner browser plugin or extension status in the browser and in Cisco Secure Desktop settings.Affected if The Cache Cleaner JAR file exists and the component is enabled in the Cisco Secure Desktop configuration
The system is affected if Cisco Secure Desktop version 3.0.x through 3.3.x is installed with the Cache Cleaner component enabled.
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 dataApply the Cisco patch for Bug ID CSCup83001 by updating Cisco Secure Desktop to the latest version. Until the patch is available, disable or remove the Cache Cleaner component and restrict user access to untrusted websites.
Fix this in Secure Desktop
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0691 — 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-2015-0691 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