CVE-2017-3105
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 · uneditedAdobe RoboHelp has an Open Redirect vulnerability. This affects versions before RH12.0.4.460 and RH2017 before RH2017.0.2.
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 confidenceAdobe RoboHelp contains an open redirect vulnerability that allows attackers to craft malicious URLs which redirect users to arbitrary external websites. This occurs due to insufficient validation of redirect parameters, enabling phishing and credential theft attacks.
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< 2017.0.1< 12.0.4.460CVSS 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.
-
Identify installed Adobe RoboHelp versionOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe RoboHelp* (or look under HKEY_CURRENT_USER for user installations). Locate the DisplayVersion value to find the installed version number.Affected if The displayed version is below 12.0.4.460 OR below 2017.0.1 (for the 2017 release line).
-
Confirm the specific release lineCheck the registry key name or product name associated with the installation. Adobe RoboHelp 12.x uses a different version numbering than Adobe RoboHelp 2017.Affected if You cannot determine whether the version is in the 12.x line or 2017 line, making version comparison ambiguous.
-
Verify RoboHelp web outputs or server components are exposedIf your RoboHelp project publishes to WebHelp or uses RoboHelp Server, check if the generated help content is accessible via HTTP/HTTPS from external or untrusted networks.Affected if RoboHelp web components are publicly accessible and the installed version falls within the affected ranges.
-
Review redirect parameter handling in published contentInspect the published WebHelp output files (typically in the output folder) and look for redirect parameters in URLs (such as rh_alert, redirect, or similar query parameters that control page navigation).Affected if The output contains redirect parameters that accept external URLs without validation (the vulnerable code pattern is present).
You are affected if your installed Adobe RoboHelp version is below 12.0.4.460 (for version 12.x releases) or below 2017.0.1 (for the 2017 release), AND your help content is accessible via web server with redirect functionality exposed.
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 data12.0.4.4602017.0.1
Upgrade Adobe RoboHelp to version RH12.0.4.460 or later, or RH2017.0.2 or later. Alternatively, implement URL validation to reject redirects to external untrusted domains.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3105 — 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-3105 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