Unity ConnectionApplication · Cisco
CVE-2020-3130
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 · uneditedA vulnerability in the web management interface of Cisco Unity Connection could allow an authenticated remote attacker to overwrite files on the underlying filesystem. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web management interface. A successful exploit could allow the attacker to overwrite files on the underlying filesystem of an affected system. Valid administrator credentials are required to access the system.
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 confidenceA file write vulnerability in the web management interface of Cisco Unity Connection due to insufficient input validation. An authenticated attacker with administrator credentials can overwrite arbitrary files on the underlying filesystem by sending crafted HTTP requests to the web management interface.
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
Unity ConnectionApplication
>= 11.0, < 11.5su7>= 12.0, < 12.5su2CVSS 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
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
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 Unity Connection is installedCheck for Unity Connection installation by reviewing installed software packages or checking system services. On the server, run: 'show version' in Cisco CLI or check Windows Add/Remove Programs depending on deployment.Affected if The product is present on the system.
-
Determine installed version of Cisco Unity ConnectionAccess the Unity Connection administration interface and navigate to About page, or run 'show version' command in Cisco Unified Communications Manager CLI. Compare version number to affected ranges: 11.0 through 11.5su6, or 12.0 through 12.5su1.Affected if Installed version falls within >= 11.0 and < 11.5su7, or >= 12.0 and < 12.5su2.
-
Verify web management interface is enabledCheck Unity Connection administration console accessibility by attempting to reach the web interface URL (typically https://hostname/cuadmin). Confirm the service is active in Cisco Unified Serviceability > Service Activation.Affected if Web management interface is accessible and active.
-
Confirm administrative accounts existReview Cisco Unity Connection user accounts with administrator privileges via the administration console under User Settings > Administrator accounts. Check for any unexpected or unauthorized admin accounts.Affected if Any administrator-level accounts are present in the system.
-
Inspect for suspicious file modifications or HTTP trafficReview web server access logs and system audit logs for anomalous POST requests to the file upload endpoints. Check for unexpected changes to critical system files or new files in writable directories.Affected if Unusual HTTP requests targeting file write functionality or unauthorized file modifications are detected.
A system is affected if it runs a vulnerable Cisco Unity Connection version (11.0-11.5su6 or 12.0-12.5su1) with the web management interface enabled and accessible, allowing an authenticated administrator to potentially overwrite arbitrary files.
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 data11.5su712.5su2
Apply the vendor patch from Cisco for CVE-2020-3130. Restrict administrative web interface access to trusted IPs/users and implement monitoring for suspicious file write operations.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3130 — 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-2020-3130 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