dbcve.org
AppbuilderApplication · Opentext

CVE-2023-4552

HIGH · 7.1 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 23.2 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
Improper Input Validation vulnerability in OpenText AppBuilder on Windows, Linux allows Probe System Files. An authenticated AppBuilder user with the ability to create or manage existing databases can leverage them to exploit the AppBuilder server - including access to its local file system. This issue affects AppBuilder: from 21.2 before 23.2.

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

Improper input validation in OpenText AppBuilder allows authenticated users with database management privileges to probe and access local system files on the server. The vulnerability exists in database management functionality where insufficient validation of user-supplied input enables path traversal or file inclusion attacks.

MitigationUpgrade AppBuilder to version 23.2 or later to obtain the vendor patch that addresses this improper input validation issue.

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
AppbuilderApplication
Affected:>= 21.2, < 23.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify installed AppBuilder version
    Locate AppBuilder installation directory and check version metadata (about dialog, installer info, or version file in the application root)
    Affected if Installed version is 21.2 or higher but lower than 23.2
  2. Verify database management module is configured
    Check if the database management functionality is enabled in AppBuilder (look for database connection configuration, DB management UI, or related module settings)
    Affected if Database management module is present and configured in the installation
  3. Confirm user privilege assignments
    Review user roles and privilege assignments within AppBuilder to identify accounts with database management permissions
    Affected if Any user accounts are assigned database management privileges
  4. Check for exposed database management interface
    Inspect web server configuration or application routing to determine if database management endpoints are accessible over network
    Affected if Database management interface is accessible to authenticated users

Environment is affected if AppBuilder version falls within 21.2 through 23.1.x AND the database management module is configured and accessible to users with database management privileges.

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 23.2 or later
Fixed in 23.2
Interim mitigation

Upgrade AppBuilder to version 23.2 or later to obtain the vendor patch that addresses this improper input validation issue.

Recommended fix High confidence

23.2

  1. Back up the current AppBuilder configuration and all databases
  2. Stop the AppBuilder server
  3. Download OpenText AppBuilder version 23.2 or later from the OpenText support portal (support.opentext.com)
  4. Install the upgraded AppBuilder version following the vendor's installation documentation
  5. Start the AppBuilder server and verify the upgrade
  6. Log in as an authenticated user and confirm database management functionality works correctly
  7. Verify that file system access is now properly restricted per the fix

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

Fix this in Appbuilder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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