dbcve.org
Ironport AsyncosOperating system · Cisco

CVE-2013-3384

HIGH · 9.0 CVSS v2.0 Published 2013-06-27
Fix available
A fix is available. Upgrade to after 7.1.3 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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 web framework in IronPort AsyncOS on Cisco Web Security Appliance devices before 7.1.3-013, 7.5 before 7.5.0-838, and 7.7 before 7.7.0-550; Email Security Appliance devices before 7.1.5-104, 7.3 before 7.3.2-026, 7.5 before 7.5.2-203, and 7.6 before 7.6.3-019; and Content Security Management Appliance devices before 7.2.2-110, 7.7 before 7.7.0-213, and 7.8 and 7.9 before 7.9.1-102 allows remote authenticated users to execute arbitrary commands via crafted command-line input in a URL, aka Bug IDs CSCzv85726, CSCzv44633, and CSCzv24579.

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

Command injection vulnerability in the web framework of Cisco IronPort AsyncOS allows authenticated remote attackers to execute arbitrary operating system commands via crafted command-line input in URLs. This affects Web Security Appliance, Email Security Appliance, and Content Security Management Appliance devices across multiple version ranges.

MitigationApply vendor patches or upgrade to the fixed versions (WSA 7.1.3-013/7.5.0-838/7.7.0-550, ESA 7.1.5-104/7.3.2-026/7.5.2-203/7.6.3-019, SMA 7.2.2-110/7.7.0-213/7.9.1-102) as specified in Cisco advisories.

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
Ironport AsyncosOperating system
Affected:<= 7.1.3= 7.2= 7.3= 7.5= 7.6= 7.7= 7.8= 7.9

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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/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. Identify the Cisco appliance type
    Access the admin web interface or CLI and determine if the device is a Web Security Appliance (WSA), Email Security Appliance (ESA), or Content Security Management Appliance (SMA). In the CLI, run the 'systemsetup' or 'version' command to confirm the appliance model.
    Affected if The device is a Cisco WSA, ESA, or SMA running the vulnerable AsyncOS versions.
  2. Check the installed AsyncOS version
    In the appliance CLI, run the 'version' command to display the installed AsyncOS version. Alternatively, log into the web interface and navigate to System Administration > System Upgrade to view the current version.
    Affected if The displayed version is <= 7.1.3, or exactly 7.2, 7.3, 7.5, 7.6, 7.7, 7.8, or 7.9.
  3. Confirm the web interface is enabled
    In the CLI, run the 'interfaceconfig' command to verify that the web interface (HTTP or HTTPS) is enabled on an interface. Alternatively, check via the web interface under Network > IP Interfaces.
    Affected if The web interface listener is active and reachable.
  4. Verify authentication configuration
    In the web interface, navigate to System Administration > User Management to confirm whether local user accounts or external authentication (LDAP, RADIUS) are configured. Check if admin-level accounts exist.
    Affected if User authentication is configured and active, making the command injection exploitable by an authenticated attacker.

If the device is a Cisco WSA, ESA, or SMA running AsyncOS versions 7.2 through 7.9 (or <=7.1.3) with the web interface enabled and authentication configured, the environment is affected by this command injection vulnerability.

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
Upgrade available Upgrade to a release after 7.1.3
Interim mitigation

Apply vendor patches or upgrade to the fixed versions (WSA 7.1.3-013/7.5.0-838/7.7.0-550, ESA 7.1.5-104/7.3.2-026/7.5.2-203/7.6.3-019, SMA 7.2.2-110/7.7.0-213/7.9.1-102) as specified in Cisco advisories.

Recommended fix High confidence

Upgrade to the minimum fixed version for your appliance: WSA 7.1.3-013/7.5.0-838/7.7.0-550; ESA 7.1.5-104/7.3.2-026/7.5.2-203/7.6.3-019; SMA 7.2.2-110/7.7.0-213/7.9.1-102

  1. 1. Identify the IronPort/Cisco appliance type (Web Security Appliance, Email Security Appliance, or Content Security Management Appliance) and current AsyncOS version using the web interface or CLI command 'version'.
  2. 2. Determine the applicable fixed version for your appliance and current version line from: WSA: 7.1.3-013, 7.5.0-838, or 7.7.0-550; ESA: 7.1.5-104, 7.3.2-026, 7.5.2-203, or 7.6.3-019; SMA: 7.2.2-110, 7.7.0-213, or 7.9.1-102.
  3. 3. Back up the appliance configuration via the web interface (System Administration > Configuration File) or CLI command 'saveconfig'.
  4. 4. Download the appropriate AsyncOS upgrade image from Cisco (requires valid service contract) at tools.cisco.com.
  5. 5. Upload the upgrade image via the web interface (System Administration > Upgrade) or CLI command 'upgrade'.
  6. 6. Reboot the appliance when prompted and verify the new version after the upgrade completes.
  7. 7. Validate that the configuration was preserved and the appliance is functioning correctly.
Caveat Review release notes for your specific version upgrade to check for any configuration or behavioral changes; test in a non-production environment first if possible

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

Fix this in Ironport Asyncos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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