dbcve.org
CrsApplication · Cisco

CVE-2009-2047

HIGH · 9.0 CVSS v2.0 Published 2009-07-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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
Directory traversal vulnerability in the Administration interface in Cisco Customer Response Solutions (CRS) before 7.0(1) SR2 in Cisco Unified Contact Center Express (aka CCX) server allows remote authenticated users to read, modify, or delete arbitrary files via unspecified vectors.

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
How this class of weakness works · CWE-22

A file path is built from user input without being confined, so sequences like “../” let an attacker step outside the intended directory. That can expose configuration, credentials, or source code, and in the worst case lets an attacker write files where they shouldn't. A durable fix resolves and canonicalises the path, then rejects anything that escapes a known-safe base directory.

General guidance for the path traversal class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
CrsApplication
Affected:= 3.5= 4.0= 4.1= 4.5= 5.0= 6.0= 7.0
Customer Response ApplicationsApplication
Affected:= 3.5
Ip QmApplication
Affected:= 3.5
Unified CcxApplication
Affected:= 3.5= 4.0\(1\)= 4.0\(3\)= 4.0\(4\)= 4.0\(5\)= 4.0\(5a\)= 4.5\(1\)= 4.5\(2\)= 5.0\(1\)= 6.0\(1\)= 7.0\(1\)
Unified Ip Contact Center ExpressApplication
Affected:= 3.0= 5.0\(1\)= 6.0\(1\)= 7.0
Unified Ip IvrApplication
Affected:= 3.0= 3.1= 4.0= 4.1= 4.5= 5.0= 6.0= 7.0= 7.0\(1\)

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

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
Patch available Apply the vendor patch
Vendor patch www.cisco.com →
Recommended fix High confidence

7.0(1) SR2 or later

  1. Identify the current version of Cisco Customer Response Solutions (CRS) or Unified CCX by checking the Administration interface or using the 'utils system version' command
  2. Review the Cisco CRS/CCX upgrade guide and release notes for version 7.0(1) SR2 to ensure compatibility with your environment
  3. Plan maintenance window as upgrade will require service interruption
  4. Download Cisco CRS 7.0(1) SR2 or later from Cisco.com or use Cisco Unified Operating System Administration to perform the upgrade
  5. Execute the upgrade following Cisco's standard CRS/CCX upgrade procedures
  6. After upgrade, verify the Administration interface is accessible and the vulnerability is resolved by confirming version 7.0(1) SR2 or later is installed
Caveat Major version upgrade from pre-7.0 to 7.0(1) SR2 may require compatibility checks with existing scripts, integrations, and hardware; test in non-production environment first

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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