dbcve.org
Engineering Requirements Management DoorsApplication · Ibm

CVE-2023-50305

MEDIUM · 5.1 CVSS v3.1 Published 2024-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click

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 Engineering Requirements Management DOORS 9.7.2.7 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 273336.

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

IBM Engineering Requirements Management DOORS version 9.7.2.7 ships with weak default password requirements, not enforcing minimum complexity, length, or expiration policies. This allows users to create easily guessable passwords, increasing susceptibility to brute-force or credential stuffing attacks.

MitigationConfigure IBM DOORS to enforce strong password policies including minimum length requirements, complexity rules, and password expiration intervals through the DOORS administration console or related configuration files.

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
Engineering Requirements Management DoorsApplication
Affected:= 9.7.2.7
Engineering Requirements Management Doors Web AccessApplication
Affected:= 9.7.2.7

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
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/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. Verify IBM DOORS version
    Locate the installed DOORS version by checking the application itself (Help > About IBM DOORS) or the installation directory for version metadata files. For DOORS Web Access, check the web application version information accessible through the administration interface.
    Affected if The installed version is exactly 9.7.2.7 for either DOORS client or DOORS Web Access.
  2. Access DOORS administration console
    Log into the DOORS administration console as an administrator user. Navigate to the password policy or security settings section where authentication configuration is managed.
    Affected if You can access the administration console without restriction, indicating default or weak admin credentials may be in use.
  3. Inspect password policy configuration
    Within the DOORS administration console, locate the password policy settings. Check whether minimum password length, complexity requirements (uppercase, lowercase, numeric, special characters), and password expiration intervals are configured and enabled.
    Affected if Password policy settings show no minimum length configured, complexity requirements are disabled or absent, and no password expiration policy is defined.
  4. Check configuration files for password settings
    Examine DOORS configuration files (typically in the installation directory or conf folder) for password policy parameters. Look for settings related to password complexity, minimum length, and expiration that may be defined in doors.conf, dwa.conf, or related configuration files.
    Affected if Configuration files contain no password policy entries or show values set to disabled/none for complexity and length requirements.
  5. Review authentication security logs
    Check DOORS server logs or audit logs for any indicators of brute-force attempts, unusual login patterns, or security events related to authentication. Also verify if the system allows unlimited login attempts without account lockout.
    Affected if Logs show successful authentication with weak passwords or no account lockout policy is enforced after failed attempts.

A user is affected if they run IBM DOORS or DOORS Web Access version 9.7.2.7 and the password policy configuration shows no enforced minimum length, complexity rules, or expiration requirements.

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

Configure IBM DOORS to enforce strong password policies including minimum length requirements, complexity rules, and password expiration intervals through the DOORS administration console or related configuration files.

Fix this in Engineering Requirements Management Doors Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50305 — 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-2023-50305 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