dbcve.org
Secure Services ClientApplication · Cisco

CVE-2007-1067

HIGH · 7.2 CVSS v2.0 Published 2007-02-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Cisco Secure Services Client (CSSC) 4.x, Trust Agent 1.x and 2.x, Cisco Security Agent (CSA) 5.0 and 5.1 (when a vulnerable Trust Agent has been deployed), and the Meetinghouse AEGIS SecureConnect Client do not properly parse commands, which allows local users to gain privileges via unspecified vectors, aka CSCsh30624.

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 confidence

Local privilege escalation vulnerability in multiple Cisco and Meetinghouse client security products due to improper command parsing. Allows local authenticated users to gain elevated privileges through unspecified vectors in Cisco Secure Services Client, Trust Agent, Cisco Security Agent, and AEGIS SecureConnect Client.

MitigationApply vendor-supplied patches or upgrade to patched versions of affected software; limit local user access and remove unnecessary local administrative accounts where possible.

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 Services ClientApplication
Affected:= 4.x
Security AgentApplication
Affected:= 5.0= 5.1
Trust AgentApplication
Affected:= 1
Aegis Secureconnect ClientApplication
Affected:= windows_platform

CVSS 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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check for Cisco Secure Services Client installation
    On Windows, open Add/Remove Programs or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Cisco Secure Services Client'. Alternatively, check Program Files folder for Cisco Secure Services Client installation directory.
    Affected if The software is installed and the version is 4.x (any 4.x release)
  2. Check for Cisco Security Agent installation
    On Windows, open Add/Remove Programs or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Cisco Security Agent'. Check Program Files for 'Cisco Security Agent' folder.
    Affected if The software is installed and the version is 5.0 or 5.1
  3. Check for Cisco Trust Agent installation
    On Windows, open Add/Remove Programs or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Cisco Trust Agent'. Check Program Files for 'Cisco Trust Agent' folder.
    Affected if The software is installed and the version is 1.x
  4. Check for Meetinghouse Aegis SecureConnect Client installation
    On Windows, open Add/Remove Programs or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Aegis' or 'SecureConnect'. Check Program Files for Meetinghouse folders.
    Affected if The software is installed on a Windows platform (any version)

A user is affected if any of these four products are installed with the specified vulnerable versions, as the privilege escalation requires local authenticated access to the system running the vulnerable software.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or upgrade to patched versions of affected software; limit local user access and remove unnecessary local administrative accounts where possible.

Fix this in Secure Services Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1067 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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