Registered Envelope ServiceApplication · Cisco
CVE-2017-12320
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 · uneditedMultiple vulnerabilities in the web interface of the Cisco Registered Envelope Service (a cloud-based service) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack or redirect a user of the affected service to an undesired web page. The vulnerabilities are due to insufficient validation of user-supplied input by the web-based management interface of the affected service. An attacker could exploit these vulnerabilities by persuading a user to click a malicious link or by sending an HTTP request that could cause the affected service to redirect the request to a specified malicious URL. A successful exploit could allow the attacker to execute arbitrary script code in the context of the web interface of the affected system or allow the attacker to access sensitive browser-based information on the affected system. These types of exploits could also be used in phishing attacks that send users to malicious websites without their knowledge. Cisco Bug IDs: CSCve77195, CSCve90978, CSCvf42310, CSCvf42703, CSCvf42723, CSCvf46169, CSCvf49999.
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 · moderate confidenceMultiple XSS and open redirect vulnerabilities in Cisco Registered Envelope Service web interface stem from insufficient validation of user-supplied input. An unauthenticated remote attacker can exploit these by persuading users to click malicious links or sending crafted HTTP requests, enabling arbitrary script execution in the web interface context or redirection to attacker-controlled URLs.
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
Registered Envelope ServiceApplication
all versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm use of Cisco Registered Envelope ServiceIdentify whether your organization uses the Cisco Registered Envelope Service web interface (typically accessed at envelopes.cisco.com or through Cisco email encryption). Check for any bookmarks, usage records, or integrations with Cisco email encryption.Affected if Your organization actively uses the Cisco Registered Envelope Service web interface.
-
Review web traffic logs for XSS attempt patternsSearch HTTP access logs for requests to the Cisco Registered Envelope Service containing suspicious patterns such as <script>, javascript:, onerror=, onload=, or other HTML/script injection attempts in URL parameters.Affected if Logs contain requests with script injection payloads sent to the envelope service endpoints.
-
Review logs for open redirect patternsSearch logs for parameter values containing attacker-controlled domains, such as parameters named 'url', 'redirect', 'next', or 'dest' containing external URLs or IP addresses in requests to the service.Affected if Logs contain requests with redirect parameters pointing to unexpected external domains.
-
Check for unexpected cookie or header manipulationExamine browser developer tools or proxy logs when accessing the service to verify that no unexpected Set-Cookie headers, Location redirects, or X-Frame-Options overrides are occurring beyond normal service behavior.Affected if Unexpected cookies are being set or unexpected redirects occur during normal use of the service.
-
Monitor for user reports of suspicious behaviorQuery users about any unusual pop-ups, browser warnings, or unexpected redirects they may have experienced when using the Cisco Registered Envelope Service, or when clicking links in encrypted emails.Affected if Users report script execution alerts, unexpected redirects, or anomalous behavior when using the service.
You are affected if your organization uses the Cisco Registered Envelope Service and there are indicators of exploitation (suspicious requests in logs, unexpected redirects, or user reports of XSS/open redirect behavior) since all versions of this cloud service are vulnerable.
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 dataSince this is a cloud-based SaaS service, remediation requires Cisco to patch their infrastructure. Implement compensating controls such as browser-based security extensions, user awareness training about malicious links, and monitor for official Cisco patches. Consider using browser-based XSS filters orContent Security Policy headers as interim protections.
Fix this in Registered Envelope Service
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12320 — 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-2017-12320 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