dbcve.org
DominoApplication · Ibm

CVE-2016-6113

MEDIUM · 6.1 CVSS v3.0 Published 2017-02-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
IBM Verse 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.

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 confidence

IBM Verse contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can inject malicious JavaScript code into the application which executes in the browsers of other users viewing the compromised content, potentially leading to session hijacking and credentials disclosure within trusted sessions.

MitigationApply vendor-supplied patches from IBM. Implement output encoding and input validation for all user-supplied content rendered in the Web UI as an interim measure.

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
DominoApplication
Affected:= 8.5.1.0= 8.5.1.1= 8.5.1.2= 8.5.1.3= 8.5.1.4= 8.5.1.5= 8.5.2.0= 8.5.2.1= 8.5.2.2= 8.5.2.3= 8.5.2.4= 8.5.3.0
InotesApplication
Affected:= 8.5.1.0= 8.5.1.1= 8.5.1.2= 8.5.1.3= 8.5.1.4= 8.5.1.5= 8.5.2.0= 8.5.2.1= 8.5.2.2= 8.5.2.3= 8.5.3.0= 8.5.3.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Domino installation
    Check for IBM Domino installation by looking for Domino directory structure, or run 'domino -v' or check the Program Files/IBM/Domino directory. Also check Windows Services for IBM Domino Server service.
    Affected if IBM Domino version matches 8.5.1.0 through 8.5.3.0 and the Web UI (iNotes) is enabled and accessible to users
  2. Identify IBM iNotes installation
    Check if iNotes is available by accessing the iNotes web URL (typically /iNotes/ or /names.nsf on the Domino server). Verify the iNotes version through the server console or by examining the iNotes installation directory.
    Affected if IBM iNotes version matches 8.5.1.0 through 8.5.3.1 and the Web UI is enabled
  3. Confirm Web UI is enabled
    Verify the Domino HTTP task is running (type 'show task' on server console). Check if iNotes is accessible by visiting the server's iNotes URL in a browser or by examining the iNotes NSF database files on the server.
    Affected if The HTTP task is running and iNotes Web UI is accessible to end users
  4. Compare installed versions to affected ranges
    Document the exact version of IBM Domino (should be 8.5.1.0 through 8.5.3.0) or IBM iNotes (should be 8.5.1.0 through 8.5.3.1) installed. Compare against these specific version numbers to determine if the environment falls within the affected range.
    Affected if The installed version exactly matches one of the listed affected versions (note: only the exact versions listed are vulnerable, not version ranges)

The environment is affected if IBM Domino or IBM iNotes is installed and the version exactly matches one of the listed affected versions (8.5.1.0-8.5.3.0 for Domino, 8.5.1.0-8.5.3.1 for iNotes) with the Web UI enabled and accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches from IBM. Implement output encoding and input validation for all user-supplied content rendered in the Web UI as an interim measure.

Fix this in Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-6113 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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