dbcve.org
Security AgentApplication · Cisco

CVE-2011-0364

HIGH · 10.0 CVSS v2.0 Published 2011-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
The Management Console (webagent.exe) in Cisco Security Agent 5.1, 5.2, and 6.0 before 6.0.2.145 allows remote attackers to create arbitrary files and execute arbitrary code via unspecified parameters in a crafted st_upload request.

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 confidence

The Management Console (webagent.exe) in Cisco Security Agent versions 5.1, 5.2, and 6.0 before 6.0.2.145 contains an unauthenticated file upload vulnerability. Remote attackers can exploit unspecified parameters in a crafted st_upload request to create arbitrary files on the affected system and execute arbitrary code with the privileges of the webagent.exe process.

MitigationUpgrade Cisco Security Agent to version 6.0.2.145 or later to remediate this vulnerability. If upgrading is not immediately possible, consider restricting network access to the Management Console port or disabling the web-based Management Console if not required.

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
Security AgentApplication
Affected:= 5.1= 5.2= 6.0

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

AV:N/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. Verify Cisco Security Agent is installed
    Check for the presence of Cisco Security Agent on the system by looking for the installation directory or checking system services for the Cisco Security Agent service.
    Affected if Cisco Security Agent is installed.
  2. Identify installed version
    Use the system's installed programs list, or check the version information of the webagent.exe file in the Cisco Security Agent installation directory, or run the Cisco Security Agent management command to retrieve the version.
    Affected if The installed version is 5.1, 5.2, or 6.0 (any version before 6.0.2.145).
  3. Confirm Management Console is enabled
    Check if the Management Console web service (webagent.exe) is running as a service or process, or check if the Management Console port is listening on the system.
    Affected if The Management Console (webagent.exe) is running and accessible.
  4. Check Management Console network exposure
    Determine if the Management Console port is exposed to the network or if it is bound to accessible network interfaces, as the vulnerability is exploitable remotely without authentication.
    Affected if The Management Console is network-accessible from untrusted networks.

A system is affected if Cisco Security Agent versions 5.1, 5.2, or 6.0 are installed with the Management Console enabled and accessible, and the version is earlier than 6.0.2.145.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco Security Agent to version 6.0.2.145 or later to remediate this vulnerability. If upgrading is not immediately possible, consider restricting network access to the Management Console port or disabling the web-based Management Console if not required.

Recommended fix High confidence

6.0.2.145 or later

  1. 1. Identify the current version of Cisco Security Agent installed by checking the Management Console or using system inventory tools.
  2. 2. Download Cisco Security Agent version 6.0.2.145 or later from the Cisco website or your authorized Cisco distribution channel.
  3. 3. Review the Cisco Security Agent upgrade documentation for your specific version.
  4. 4. Schedule a maintenance window to perform the upgrade, ensuring appropriate backups are in place.
  5. 5. Apply the upgrade package to all affected systems running versions 5.1, 5.2, or 6.0.
  6. 6. Verify the upgrade was successful by checking the version number after installation.
  7. 7. Test the Management Console functionality to ensure the st_upload request handler is working correctly after the patch.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-0364 — 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-2011-0364 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