CVE-2017-1335
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 RELM 4.0, 5.0, and 6.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 126243.
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 confidenceIBM RELM versions 4.0, 5.0, and 6.0 contain a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code through user-supplied input fields, which executes in the browsers of other users viewing the affected interface. This can enable session hijacking and credential theft within trusted sessions.
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= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2= 6.0.0= 6.0.1= 6.0.2= 6.0.3CVSS 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 IBM RELM installation versionLocate the RELM installation directory and check version files such as about.html, version.info, or the IBM Installation Manager registry. Alternatively, access the Web UI login page and look for version information in the footer or About section.Affected if The installed version matches any of: 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0.0, 5.0.1, 5.0.2, 6.0.0, 6.0.1, 6.0.2, or 6.0.3
-
Confirm Web UI is enabledVerify that the RELM Web UI service is running and accessible. Check the server configuration for webui.enabled or similar settings, or attempt to access the Web UI URL (typically http://hostname:9080/relm or similar).Affected if The Web UI is accessible and the application is running with user-supplied input fields that get displayed back in the interface
-
Identify input fields in the Web UILog into the RELM Web UI and navigate to common input areas such as user profile fields, project descriptions, artifact metadata, or search fields. These are typical locations where user-supplied data is stored and displayed.Affected if User-supplied input fields exist and data entered is rendered without context-aware encoding, allowing script injection to persist and execute when other users view the content
You are affected if your IBM RELM version is 4.0.3 through 6.0.3 and the Web UI is accessible with user input fields that display data without proper encoding.
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 dataImplement context-aware output encoding and input validation for all user-supplied data displayed in the Web UI. Apply Content Security Policy (CSP) headers to mitigate XSS execution. Upgrade to a patched version of IBM RELM if available from IBM support.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1335 — 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-1335 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