Webcenter InteractionApplication · Oracle

CVE-2018-16955

MEDIUM · 6.1 CVSS v3.0 Published 2018-09-18
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
The login function of Oracle WebCenter Interaction Portal 10.3.3 is vulnerable to reflected cross-site scripting (XSS). The content of the in_hi_redirect parameter, when prefixed with the https:// scheme, is unsafely reflected in a HTML META tag in the HTTP response. NOTE: this CVE is assigned by MITRE and isn't validated by Oracle because Oracle WebCenter Interaction Portal is out of support.

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 confidence

The login function of Oracle WebCenter Interaction Portal 10.3.3 contains a reflected XSS vulnerability. The in_hi_redirect parameter, when prefixed with https://, is unsafely reflected into an HTML META tag in the HTTP response without proper encoding or sanitization, allowing injection of malicious scripts.

MitigationSince Oracle WebCenter Interaction Portal is out of support with no official patch available, implement input validation and output encoding on the in_hi_redirect parameter, or deploy a WAF rule to filter malicious payloads in this parameter.

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
Webcenter InteractionApplication
Affected:= 10.3.3

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. Confirm Oracle WebCenter Interaction installation
    Identify if Oracle WebCenter Interaction Portal is deployed in your environment. Check for web applications responding on typical ports (8080, 8090, 80) or search for process named 'ptportal' or 'oracle webcenter' on servers.
    Affected if Oracle WebCenter Interaction Portal 10.3.3 is installed and accessible.
  2. Verify the exact version number
    Access the portal login page and check the version information typically displayed in the footer, or query the application's /about page, or run: java -jar ptversion.jar against the installation directory if available.
    Affected if The installed version is exactly 10.3.3.
  3. Locate the login page endpoint
    Identify the login URL, commonly at /portal/login or /login. The vulnerable parameter in_hi_redirect is processed on the login form submission.
    Affected if The login page is accessible and accepts the in_hi_redirect parameter.
  4. Test for reflected XSS in in_hi_redirect
    Submit a login request with in_hi_redirect set to 'https://';view-source to check if it appears unsanitized inside an HTML META tag. Alternatively, inject a simple payload like 'https://test' and inspect the response HTML for unencoded reflection.
    Affected if The in_hi_redirect parameter value is reflected directly into the response HTML without encoding, appearing inside a META tag.

You are affected if Oracle WebCenter Interaction Portal 10.3.3 is running and the in_hi_redirect parameter on the login page is reflected unsanitized in the HTTP response.

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

Since Oracle WebCenter Interaction Portal is out of support with no official patch available, implement input validation and output encoding on the in_hi_redirect parameter, or deploy a WAF rule to filter malicious payloads in this parameter.

Fix this in Webcenter Interaction Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-16955 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-16955 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