dbcve.org
VerticaApplication · Opentext

CVE-2023-7248

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-15
Fix available
A fix is available. Upgrade to 11.1.1-25 / 12.0.4-19 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
Certain functionality in OpenText Vertica Management console might be prone to bypass via crafted requests.  The vulnerability would affect one of Vertica’s authentication functionalities by allowing specially crafted requests and sequences. This issue impacts the following Vertica Management Console versions: 10.x 11.1.1-24 or lower 12.0.4-18 or lower Please upgrade to one of the following Vertica Management Console versions: 10.x to upgrade to latest versions from below. 11.1.1-25 12.0.4-19 23.x 24.x

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 Vertica Management Console contains an authentication bypass vulnerability where specially crafted requests and sequences can bypass authentication controls in one of the authentication functionalities. This critical flaw allows unauthenticated attackers to potentially gain unauthorized access to the system.

MitigationUpgrade Vertica Management Console to version 11.1.1-25, 12.0.4-19, or any 23.x/24.x version to patch the authentication bypass vulnerability.

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
VerticaApplication
Affected:>= 10.0.0-0, <= 10.1.1-26>= 11.0.0-0, < 11.1.1-25>= 12.0.0-0, < 12.0.4-19

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 Vertica version
    Run 'vsql -c "SELECT VERSION();"' or check /opt/vertica/bin/vertica -V output. On Linux, also check /opt/vertica/packages/dbms_pkg/scripts/installed_packages for package versions.
    Affected if The version falls within 10.0.0-0 through 10.1.1-26, 11.0.0-0 through 11.1.1-24, or 12.0.0-0 through 12.0.4-18.
  2. Locate Management Console port and service
    Check for processes listening on port 5444 or 5434 using 'netstat -tlnp | grep -E "(5444|5434)"' or review /etc/httpd/conf.d/vertica_ui.conf for the configured port.
    Affected if Management Console service is running and exposed on a network port.
  3. Verify Management Console is reachable
    Attempt HTTP/HTTPS request to the Management Console URL such as https://hostname:5444 or check if the service responds to unauthenticated requests.
    Affected if Management Console endpoint responds without authentication.
  4. Check for unauthorized access indicators
    Review Management Console access logs under /var/www/vertica/ logs or /opt/vertica/ui/logs for suspicious unauthenticated requests, especially to authentication-related endpoints.
    Affected if Log entries show successful unauthenticated access or anomalous authentication sequences.
  5. Inspect authentication configuration
    Examine /opt/vertica/ui/conf/ or /etc/vertica_management_console.conf for authentication settings. Look for non-default authentication methods or disabled security controls.
    Affected if Authentication configuration has been modified from defaults or shows bypass-enabled settings.

A user is affected if their Vertica version is 10.0.0-0 through 10.1.1-26, 11.0.0-0 through 11.1.1-24, or 12.0.0-0 through 12.0.4-18 AND the Management Console is network-accessible.

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 11.1.1-25 / 12.0.4-19 or later
Fixed in 11.1.1-2512.0.4-19
Interim mitigation

Upgrade Vertica Management Console to version 11.1.1-25, 12.0.4-19, or any 23.x/24.x version to patch the authentication bypass vulnerability.

Recommended fix High confidence

11.1.1-25 (for 11.x), 12.0.4-19 (for 12.x), or latest 23.x/24.x release

  1. Backup the Vertica Management Console configuration and any custom settings
  2. Ensure you have database backups before proceeding with any Management Console upgrade
  3. Download the fixed Vertica Management Console version appropriate for your current major version: 11.1.1-25, 12.0.4-19, or newer 23.x/24.x releases
  4. Stop the Vertica Management Console service before upgrading
  5. Install the updated Vertica Management Console package for your version
  6. After installation, verify the Management Console service starts successfully
  7. Confirm the new version by checking the Management Console UI or command line (e.g., admintools or vsql SELECT VERSION())
  8. Validate that authentication functionality works correctly with the updated version
Caveat Upgrading between major versions (e.g., 10.x to 11.x or 12.x to 23.x) may require compatibility checks with existing workflows; test in non-production first

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

Fix this in Vertica Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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