CVE-2013-1223
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 · uneditedThe log viewer in Cisco Unified Customer Voice Portal (CVP) Software before 9.0.1 ES 11 does not properly validate an unspecified parameter, which allows remote attackers to read arbitrary files via a crafted (1) HTTP or (2) HTTPS request, aka Bug ID CSCub38372.
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 confidenceThe log viewer component in Cisco Unified Customer Voice Portal (CVP) Software before version 9.0.1 ES 11 lacks proper input validation on an unspecified parameter, allowing remote attackers to use path traversal sequences (e.g., '../') in crafted HTTP or HTTPS requests to read arbitrary files on the affected system. This is a directory traversal vulnerability in the web-based log viewer.
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<= 9.0\(1\)= 3.0= 3.6\(10\)= 4.0= 4.0\(2\)= 4.1= 7.0= 7.0\(2\)= 8.0\(1\)= 8.5\(1\)= 9.0CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Cisco CVP is installedCheck for CVP installation directories (commonly under C:\CVP or /opt/cvp), or look for CVP services running on the system using 'sc query' on Windows or 'ps aux' on LinuxAffected if Cisco Unified Customer Voice Portal software is found on the system
-
Determine the installed CVP versionCheck the CVP version file in the installation directory, or run 'cvp_version' command if available, or look in Windows Registry under HKLM\SOFTWARE\Cisco\CVPAffected if The installed version matches one of the affected versions: 3.0, 3.6(10), 4.0, 4.0(2), 4.1, 7.0, 7.0(2), 8.0(1), 8.5(1), 9.0, or any version <= 9.0(1)
-
Verify the web-based log viewer is accessibleCheck if the CVP web management interface ports are listening (typically ports 80, 443, or 8080, 8443). Use 'netstat -an | findstr LISTENING' on Windows or 'netstat -tuln' on LinuxAffected if The CVP web interface ports are open and listening for HTTP/HTTPS connections
-
Confirm the log viewer component is enabledAccess the CVP web interface and navigate to the log viewer section (typically /cvp/logviewer or similar path), or check the CVP configuration files for enabled web componentsAffected if The log viewer web component is exposed and accessible via the CVP web interface
You are affected if Cisco CVP is installed with a version <= 9.0(1) and the web-based log viewer component is accessible on your network.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Cisco CVP 9.0.1 ES 11 or later to obtain the patched version. If immediate upgrading is not feasible, restrict network access to CVP management interfaces using firewalls or ACLs to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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