Registered Envelope ServiceApplication · Cisco
CVE-2017-3889
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 interface of the Cisco Registered Envelope Service could allow an unauthenticated, remote attacker to redirect a user to a undesired web page, aka an Open Redirect. This vulnerability affects the Cisco Registered Envelope cloud-based service. More Information: CSCvc60123. Known Affected Releases: 5.1.0-015.
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 confidenceOpen Redirect vulnerability in Cisco Registered Envelope Service web interface allows unauthenticated remote attackers to craft malicious URLs that appear legitimate but redirect users to attacker-controlled websites. This is commonly exploited in phishing attacks to increase credibility of malicious links.
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
= 5.1.0-015CVSS 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 Cisco Registered Envelope Service is in useReview your organization's software inventory or ask IT administrators whether Cisco Registered Envelope Service (CRES) is deployed. Check for related email encryption or secure messaging products.Affected if The organization uses Cisco Registered Envelope Service
-
Identify the installed versionAccess the CRES administration console or check the software version displayed in the service interface. If using the cloud version, verify the version through the service provider portal or contact Cisco support.Affected if The version is exactly 5.1.0-015
-
Verify web interface accessibilityDetermine if the CRES web interface is accessible from the internet by attempting to reach the login page externally or reviewing firewall/load balancer access logs for cres.cisco.com or your organization's CRES URL.Affected if The web interface is externally accessible and the version is 5.1.0-015
-
Review URL redirect configurationsInspect HTTP traffic logs or web application firewall logs for unusual redirect parameters in CRES URLs, such as 'redirect=' or 'url=' parameters pointing to external domains.Affected if Suspicious redirect parameters are found in CRES traffic logs
A user is affected if their deployment uses Cisco Registered Envelope Service version exactly 5.1.0-015 with an accessible web interface.
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 dataContact Cisco support to confirm the vulnerability has been patched in the cloud service. Implement email security controls and user awareness training to mitigate phishing attempts leveraging this open redirect.
Fix this in Registered Envelope Service
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3889 — 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-3889 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