dbcve.org
Content Security Management ApplianceHardware / appliance · Cisco

CVE-2013-3395

MEDIUM · 6.8 CVSS v2.0 Published 2013-07-02
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
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
Cross-site request forgery (CSRF) vulnerability in the web framework on Cisco IronPort Web Security Appliance (WSA) devices, Email Security Appliance (ESA) devices, and Content Security Management Appliance (SMA) devices allows remote attackers to hijack the authentication of arbitrary users, aka Bug IDs CSCuh70263, CSCuh70323, and CSCuh26634.

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

Cross-site request forgery (CSRF) vulnerability in the web framework of Cisco IronPort security appliances (WSA, ESA, and SMA). Attackers can craft malicious requests that trick authenticated users into performing unintended actions, hijacking their session authentication.

MitigationApply the relevant Cisco firmware/software update for CSCuh70263, CSCuh70323, or CSCuh26634. Additionally, configure anti-CSRF tokens in the web framework or validate Referer/Origin headers on state-changing requests as a defense-in-depth measure.

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
Content Security Management ApplianceHardware / appliance
Affected:all versions
Web Security ApplianceHardware / appliance
Affected:all versions
Email Security Appliance FirmwareOperating system
Affected:all versions

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 appliance model
    Access the appliance administrative interface or use CLI command 'ls' or check the product model number displayed in the web UI header or login page
    Affected if The model is Cisco Web Security Appliance (WSA), Cisco Email Security Appliance (ESA), or Cisco Content Security Management Appliance (SMA)
  2. Verify the web interface is enabled
    Check if the appliance web UI is accessible via HTTPS on port 8443 (default) or port 443. Log into the web interface and navigate to Network Settings or Administration > System Administration > Network Configuration to confirm web services are running
    Affected if The web interface is accessible and running
  3. Confirm no anti-CSRF token protection is configured
    In the web UI, navigate to Administration > System Administration > Feature Keys or check under Security Services > Anti-Spam > Settings to verify if anti-CSRF tokens are enabled. Alternatively, check the HTTP responses for the presence of security tokens in form submissions
    Affected if Anti-CSRF tokens are not configured or not present in web form submissions
  4. Check Referer/Origin header validation
    Inspect the web framework configuration files or proxy logs to determine if Referer or Origin header validation is enforced on state-changing requests (POST/PUT/DELETE operations)
    Affected if Referer/Origin header validation is not enabled or enforced

If you have a Cisco WSA, ESA, or SMA appliance with the web interface enabled and no anti-CSRF token protection or Referer/Origin validation is configured, your environment is affected by this 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco firmware/software update for CSCuh70263, CSCuh70323, or CSCuh26634. Additionally, configure anti-CSRF tokens in the web framework or validate Referer/Origin headers on state-changing requests as a defense-in-depth measure.

Fix this in Content Security Management Appliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

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