dbcve.org
VerticaApplication · Opentext

CVE-2025-12455

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to after 12.0.4-34 or later.
See remediation →
84/100
Remediation priority · High
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
Observable response discrepancy vulnerability in OpenText™ Vertica allows Password Brute Forcing.   The vulnerability could lead to Password Brute Forcing in Vertica management console application.This issue affects Vertica: from 10.0 through 10.X, from 11.0 through 11.X, from 12.0 through 12.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

Observable response discrepancy vulnerability in OpenText Vertica management console allows attackers to distinguish between valid and invalid credentials through different error messages, timing, or HTTP status codes, enabling password brute forcing attacks.

MitigationImplement uniform authentication responses (identical error messages, timing, and status codes) regardless of whether the username or password is incorrect to prevent user enumeration and brute force attacks.

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, <= 12.0.4-34

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/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. Identify Vertica installation and version
    Run 'vertica -V' or check /opt/vertica/bin/vertica -V to obtain the installed Vertica version number
    Affected if The installed version falls within >= 10.0.0-0 and <= 12.0.4-34
  2. Determine if Management Console is enabled
    Check if the Management Console web service is running on the default port 5444 or configured port by examining process list (ps aux | grep vertica) or netstat output
    Affected if The Management Console web interface is exposed and accessible on the network
  3. Locate Management Console configuration
    Examine the MC configuration files in /opt/vertica/mc/ or the directory where Management Console is installed for configuration files
    Affected if The Management Console is installed and configured on the system
  4. Test authentication response behavior
    Send two login requests to the Management Console URL: one with a valid username but wrong password, and another with a completely non-existent username. Compare HTTP status codes, error messages, and response times between the two attempts
    Affected if The responses differ in message content, HTTP status code, or response timing between valid-username-wrong-password and invalid-username attempts, indicating user enumeration is possible

A system is affected if Vertica version 10.0.0 through 12.0.4-34 is installed with the Management Console exposed, and the login endpoint returns distinguishable responses for valid versus invalid usernames.

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 a release after 12.0.4-34
Interim mitigation

Implement uniform authentication responses (identical error messages, timing, and status codes) regardless of whether the username or password is incorrect to prevent user enumeration and brute force attacks.

Recommended fix Moderate confidence

Upgrade to Vertica 12.0.5 or later (or the latest stable 12.X release)

  1. 1. Identify the current Vertica version installed by running: SELECT VERSION();
  2. 2. Backup all critical databases and configurations before proceeding with the upgrade
  3. 3. Download the latest Vertica server package from the OpenText/Vertica official download portal
  4. 4. Install the upgrade following Vertica's standard upgrade procedure: https://www.vertica.com/docs/latest/HTML/Content/Authoring/InstallationGuide/Upgrading/Upgrading.htm
  5. 5. After upgrade, verify the management console is accessible and test authentication functionality
  6. 6. Confirm the vulnerability is remediated by verifying that login responses are consistent (no timing or error message differences that could aid brute force attacks)
Caveat Review Vertica release notes for any backward-incompatible changes between your current version and the target upgrade version before proceeding

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

Fix this in Vertica Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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