CVE-2018-1457
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 · uneditedAn undisclosed vulnerability in IBM Rational DOORS 9.5.1 through 9.6.1.10 application allows an attacker to gain DOORS administrator privileges. IBM X-Force ID: 140208.
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 confidenceAn undisclosed vulnerability in IBM Rational DOORS versions 9.5.1 through 9.6.1.10 allows an attacker to escalate privileges to DOORS administrator level. The specific vulnerability type is not disclosed in available records, but the critical CVSS score indicates an easily exploitable privilege escalation flaw.
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>= 9.5.1, <= 9.5.1.9>= 9.5.2, <= 9.5.2.8>= 9.6.0, <= 9.6.0.7>= 9.6.1, <= 9.6.1.10>= 9.7.0, <= 9.7.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 DOORS versionLocate the DOORS client or server installation and retrieve the version information, typically found in the program's 'About' dialog, installation directory metadata, or by running the doors.exe with a version flagAffected if The installed version falls within any of these ranges: 9.5.1 through 9.5.1.9, 9.5.2 through 9.5.2.8, 9.6.0 through 9.6.0.7, 9.6.1 through 9.6.1.10, or 9.7.0 through 9.7.2
-
Review DOORS user accountsAccess the DOORS administrative interface or user management configuration to list all DOORS users and their assigned roles, noting any accounts with Administrator privilegesAffected if Unexpected or unauthorized accounts exist with Administrator-level permissions, or legitimate accounts show privilege changes not initiated by authorized administrators
-
Check for recent administrative actionsExamine DOORS audit logs, server logs, or administrative activity records for privilege escalation events, focusing on timestamps and user accounts that performed role modificationsAffected if Audit logs show privilege escalation activities performed by non-administrator accounts or by accounts without prior administrative rights
Your environment is affected if the installed DOORS version is within the listed affected ranges and there is evidence of unauthorized privilege escalation or unexpected administrator accounts.
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.
dbcve · scopedApply the appropriate IBM Rational DOORS security patch to version 9.6.1.11 or later to remediate this privilege escalation vulnerability.
IBM Rational DOORS 9.6.2.x or later, or the latest service pack beyond your current branch (e.g., 9.5.1.10+, 9.5.2.9+, 9.6.0.8+, 9.6.1.11+)
- 1. Identify the currently installed IBM Rational DOORS version by opening DOORS and navigating to Help > About DOORS, or by checking the installation directory for version information.
- 2. Determine which version branch you are currently on (9.5.1.x, 9.5.2.x, 9.6.0.x, or 9.6.1.x).
- 3. Obtain the latest interim fix or service release for your version branch from IBM Fix Central (https://www.ibm.com/support/fixcentral) by searching for Rational DOORS and the specific CVE (CVE-2018-1457).
- 4. Download the appropriate fix for your version - for 9.6.1.x users, obtain version 9.6.1.11 or later which contains the security remediation.
- 5. Back up your DOORS database and configuration files before applying any update.
- 6. Apply the fix following IBM's standard installation instructions - typically requires stopping the DOORS server, applying the interim fix, and restarting the server.
- 7. Verify the fix was applied successfully by checking the version number in Help > About DOORS shows a version beyond the affected ranges (e.g., 9.6.1.11 or higher).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1457 — 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-1457 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