What is the severity of CVE-2018-1912?

CVE-2018-1912 is classified as a high severity vulnerability due to its potential for credential disclosure through cross-site scripting.

How do I fix CVE-2018-1912?

To fix CVE-2018-1912, you should upgrade IBM DOORS Next Generation to version 6.0.7 or later where the vulnerability is addressed.

What types of systems are affected by CVE-2018-1912?

CVE-2018-1912 affects IBM Rational DOORS Next Generation versions 6.0.2 through 6.0.6.

What is the impact of CVE-2018-1912?

The impact of CVE-2018-1912 can lead to unauthorized disclosure of credentials within a trusted session due to the embedding of malicious JavaScript.

Is there a workaround for CVE-2018-1912 before a fix is applied?

Currently, the recommended approach is to apply the upgrade rather than relying on a workaround for CVE-2018-1912.

Vulnerability/
CVE-2018-1912

medium

5.4

CWE

4/3/2019

5/8/2024

CVE-2018-1912: XSS

First published: Mon Mar 04 2019(Updated: )

IBM DOORS Next Generation (DNG/RRC) 6.0.2 through 6.0.6 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: 152736.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM Rational DOORS Next Generation	>=6.0.2<=6.0.6

Remedy

http://www.ibm.com/support/docview.wss?uid=ibm10873254

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-1912?
CVE-2018-1912 is classified as a high severity vulnerability due to its potential for credential disclosure through cross-site scripting.
How do I fix CVE-2018-1912?
To fix CVE-2018-1912, you should upgrade IBM DOORS Next Generation to version 6.0.7 or later where the vulnerability is addressed.
What types of systems are affected by CVE-2018-1912?
CVE-2018-1912 affects IBM Rational DOORS Next Generation versions 6.0.2 through 6.0.6.
What is the impact of CVE-2018-1912?
The impact of CVE-2018-1912 can lead to unauthorized disclosure of credentials within a trusted session due to the embedding of malicious JavaScript.
Is there a workaround for CVE-2018-1912 before a fix is applied?
Currently, the recommended approach is to apply the upgrade rather than relying on a workaround for CVE-2018-1912.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/remedy
agent/last-modified-date
agent/author
agent/weakness
agent/severity
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/ibm
canonical/ibm rational doors next generation
version/ibm rational doors next generation/6.0.2
version/ibm rational doors next generation/6.0.6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-1912?
CVE-2018-1912 is classified as a high severity vulnerability due to its potential for credential disclosure through cross-site scripting.
How do I fix CVE-2018-1912?
To fix CVE-2018-1912, you should upgrade IBM DOORS Next Generation to version 6.0.7 or later where the vulnerability is addressed.
What types of systems are affected by CVE-2018-1912?
CVE-2018-1912 affects IBM Rational DOORS Next Generation versions 6.0.2 through 6.0.6.
What is the impact of CVE-2018-1912?
The impact of CVE-2018-1912 can lead to unauthorized disclosure of credentials within a trusted session due to the embedding of malicious JavaScript.
Is there a workaround for CVE-2018-1912 before a fix is applied?
Currently, the recommended approach is to apply the upgrade rather than relying on a workaround for CVE-2018-1912.