CVE-2018-1704
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 · uneditedIBM Platform Symphony 7.1 Fix Pack 1 and 7.1.1 and IBM Spectrum Symphony 7.1.2 and 7.2.0.2 could allow a remote attacker to conduct phishing attacks, using an open redirect attack. By persuading a victim to visit a specially-crafted Web site, a remote attacker could exploit this vulnerability to spoof the URL displayed to redirect a user to a malicious Web site that would appear to be trusted. This could allow the attacker to obtain highly sensitive information or conduct further attacks against the victim. IBM X-Force ID: 146339.
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 IBM Spectrum Symphony's web interface allows attackers to craft malicious URLs that redirect users to external malicious websites. The application fails to properly validate redirect URLs, enabling phishing attacks where users believe they are visiting a trusted IBM site.
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= 7.1= 7.1.1= 7.1.2= 7.2.0.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 IBM Symphony product and versionLocate the product installation directory and check version information files or use product-specific commands to query the installed version. Common locations include /opt/ibm/symphony or similar installation paths. Look for version manifest or about information.Affected if The installed version matches exactly 7.1, 7.1.1, 7.1.2, or 7.2.0.2 for either IBM Platform Symphony or IBM Spectrum Symphony.
-
Confirm the web interface is accessibleAccess the IBM Spectrum Symphony or IBM Platform Symphony web console URL (typically on port 8080, 8443, or similar). Verify the service is running and reachable.Affected if The web interface is exposed and responds to requests.
-
Test for open redirect vulnerability in redirect parametersCraft a URL that includes a redirect parameter pointing to an external domain, such as adding '?redirect=http://malicious-site.com' or '?next=http://attacker-controlled-site.com' to the login or portal URL. Observe whether the application redirects to the external site without validation.Affected if The application redirects to the arbitrary external domain specified in the redirect parameter without validating the URL.
You are affected if you have IBM Platform Symphony version 7.1 or 7.1.1, or IBM Spectrum Symphony version 7.1.2 or 7.2.0.2, and your web interface accepts and follows unvalidated redirect URLs to external domains.
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 vendor patches for the affected versions (7.1 FP1, 7.1.1, 7.1.2, 7.2.0.2). Implement strict URL validation ensuring redirects only allow relative paths or whitelisted trusted domains.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1704 — 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-2018-1704 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