FinesseApplication · Cisco
CVE-2019-12632
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 Cisco Finesse could allow an unauthenticated, remote attacker to bypass access controls and conduct a server-side request forgery (SSRF) attack on an affected system. The vulnerability exists because the affected system does not properly validate user-supplied input. An attacker could exploit this vulnerability by sending a crafted request to a user of the web application. A successful exploit could allow the attacker to access the system and perform unauthorized actions.
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 confidenceThis is a server-side request forgery (SSRF) vulnerability in Cisco Finesse where the web application fails to properly validate user-supplied input in crafted requests. An unauthenticated remote attacker can exploit this by tricking a user into sending a malicious request, allowing the attacker to make the server perform unauthorized requests to internal systems and bypass access controls.
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
FinesseApplication
= 11.6\(1\)= 12.0\(1\)= 12.5\(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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the installed Cisco Finesse versionLog into the Cisco Finesse admin console and navigate to System > Properties, or use the command line: show version or cat /opt/finesse/version.txt (path may vary by installation). Alternatively, check the About page in the Finesse web interface.Affected if The installed version is 11.6(1), 12.0(1), or 12.5(1)
-
Confirm the Cisco Finesse web service is running and accessibleAttempt to access the Finesse login page at https://<finesse-host>/finesse/login or the admin portal. Verify the HTTP/HTTPS service responds.Affected if The web interface is exposed and reachable, making the SSRF payload delivery possible
-
Determine if the Finesse server has direct network access to internal systemsReview network segmentation and firewall rules applied to the Finesse server. Check if the server can initiate outbound connections to internal IP ranges (e.g., RFC1918 addresses) or sensitive internal services.Affected if The Finesse server can reach internal systems, which would allow a successful SSRF attack to pivot to internal resources
-
Check for recent access logs or anomalous request patternsReview Finesse server access logs (typically in /var/log/ or accessible via the admin interface) for suspicious outbound requests, particularly those with internal IP addresses or unusual URL parameters in the HTTP referer or request body.Affected if Logs show requests to internal IP addresses or unusual URL patterns that correlate with the SSRF vulnerability being exploited
A Cisco Finesse deployment is affected if it runs version 11.6(1), 12.0(1), or 12.5(1) and has the web interface accessible to potential attackers, allowing them to inject malicious URLs that the server will request.
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 dataApply the Cisco patch for CVE-2019-12632 and implement strict input validation on URL parameters to prevent arbitrary server-side requests.
Fix this in Finesse
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12632 — 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-2019-12632 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