dbcve.org
BizmanagerApplication · Opentext

CVE-2022-35898

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-01
Fix available
A fix is available. Upgrade to 16.6.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
OpenText BizManager before 16.6.0.1 does not perform proper validation during the change-password operation. This allows any authenticated user to change the password of any other user, including the Administrator account.

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

OpenText BizManager before 16.6.0.1 contains a broken access control vulnerability in the change-password operation. The application authenticates users but fails to verify that the requesting user is authorized to change the target user's password, allowing any authenticated user to reset passwords for any account including Administrator through direct object reference manipulation.

MitigationUpgrade to BizManager version 16.6.0.1 or later. Until then, implement additional access control validation on password change endpoints to verify the authenticated user has permission to modify the specified user's credentials.

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
BizmanagerApplication
Affected:< 16.6.0.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
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 checks

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

  1. Identify installed BizManager version
    Locate the BizManager installation and check the version information, typically found in the application header, about page, or installation directory metadata. Common locations include the admin console, WAR file version manifest, or product release notes.
    Affected if The installed version is any release prior to 16.6.0.1 (e.g., 16.5.x, 16.4.x, earlier versions)
  2. Verify password change endpoint accessibility
    Confirm the BizManager web interface is accessible and the change-password functionality exists. This is typically found under user management, account settings, or admin panels depending on the deployment.
    Affected if The password change or user management interface is accessible to authenticated users without role restrictions
  3. Check authentication requirements on password operations
    Test the password change endpoint with a low-privilege authenticated user account to determine if the application permits changing passwords for other users, including Administrator accounts.
    Affected if An authenticated user (non-administrator) can successfully submit a password change request for a different user account or Administrator
  4. Review access control on user ID parameters
    If accessible, inspect whether the password change request allows manipulation of user identifiers (such as user ID, username, or account parameters) to target arbitrary accounts.
    Affected if The password change operation accepts user-identifying parameters that can be modified to reference other accounts

A user is affected if BizManager version is below 16.6.0.1 AND the password change endpoint permits authenticated users to alter passwords for accounts other than their own, including Administrator accounts.

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.

dbcve · scoped
Upgrade available Upgrade to 16.6.0.1 or later
Fixed in 16.6.0.1
Interim mitigation

Upgrade to BizManager version 16.6.0.1 or later. Until then, implement additional access control validation on password change endpoints to verify the authenticated user has permission to modify the specified user's credentials.

Recommended fix High confidence

BizManager 16.6.0.1

  1. 1. Back up the current BizManager installation, configuration files, and database before upgrading
  2. 2. Download BizManager version 16.6.0.1 or later from the official OpenText vendor portal or authorized distribution channel
  3. 3. Stop all BizManager services and ensure no active sessions are connected
  4. 4. Install the upgrade following the official OpenText BizManager upgrade documentation
  5. 5. After installation, verify the version number matches the fixed release (16.6.0.1 or later)
  6. 6. Restart BizManager services and verify normal operation
  7. 7. Test the password change functionality to confirm the vulnerability is remediated (ensure proper authorization checks are enforced)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bizmanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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