dbcve.org
VerticaApplication · Microfocus

CVE-2024-6360

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-02
Fix available
A fix is available. Upgrade to 12.0.4-30 / 23.3.0-11 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
Incorrect Permission Assignment for Critical Resource vulnerability in OpenText™ Vertica could allow Privilege Abuse and result in unauthorized access or privileges to Vertica agent apikey. This issue affects Vertica: from 10.0 through 10.X, from 11.0 through 11.X, from 12.0 through 12.X, from 23.0 through 23.X, from 24.0 through 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 · moderate confidence

This is an Incorrect Permission Assignment vulnerability in OpenText Vertica where the Vertica agent API key has improperly configured permissions. This allows privilege abuse where an attacker with limited access could potentially read or access the API key due to overly permissive settings, escalating their privileges within the Vertica system.

MitigationApply proper file system and configuration permissions to restrict access to the Vertica agent API key, ensuring only authorized Vertica components and administrators can read it. Consult Vertica documentation or patches for version-specific permission guidance.

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-30>= 23.0.0-0, < 23.3.0-11>= 23.4.0-0, < 23.4.0-13
VerticaApplication
Affected:>= 24.1.0-0, < 24.1.0-8>= 24.2.0-0, < 24.2.0-4= 24.3.0-0

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 'SELECT VERSION();' against the Vertica database or check the installed package version using the system package manager (e.g., 'rpm -q vertica' or 'dpkg -l | grep vertica')
    Affected if The installed version falls within the affected ranges: Microfocus Vertica 10.0.0-0 to 12.0.4-29, 23.0.0-0 to 23.3.0-10, or 23.4.0-0 to 23.4.0-12; OpenText Vertica 24.1.0-0 to 24.1.0-7, 24.2.0-0 to 24.2.0-3, or 24.3.0-0
  2. Determine if Vertica agent is in use
    Check for the presence of the Vertica agent process or service (e.g., look for 'vertica_agent' in running processes via 'ps aux | grep -i vertica' or check for agent-related configuration files in the Vertica installation directory)
    Affected if The Vertica agent is installed and running - the vulnerability only applies when the agent is enabled
  3. Locate the Vertica agent API key file
    Search for the agent configuration directory, typically found under the Vertica installation path (e.g., look in /opt/vertica/agent or similar configuration directories, and search for files named 'api_key', 'key', or containing 'APIKEY' or similar patterns)
    Affected if The API key file exists on the system - if the agent is in use, there should be an associated key file
  4. Check file system permissions on the API key file
    Use 'ls -la <path_to_api_key_file>' to list permissions, and verify using 'getfacl <path_to_api_key_file>' if available. Check if the file is readable by non-privileged users (permissions should not include 'r' for 'other' or group)
    Affected if Permissions allow read access by non-owner users (e.g., mode shows 'r--r--r--' or similar broader permissions, or ownership is set to a shared group that includes untrusted users)
  5. Verify ownership and access control on the API key file
    Review the file ownership (should be owned by the Vertica database administrator account or a dedicated service account) and check for any overly permissive Access Control Lists (ACLs) that grant access to unprivileged users or groups
    Affected if The file is owned by a shared or privileged group, or ACLs grant access to users beyond the intended Vertica administrators

You are affected if your Vertica version is within the affected ranges, the Vertica agent is enabled, and the API key file is readable by non-privileged users due to overly permissive file permissions.

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 12.0.4-30 / 23.3.0-11 / 23.4.0-13 or later
Fixed in 12.0.4-3023.3.0-1123.4.0-13
Interim mitigation

Apply proper file system and configuration permissions to restrict access to the Vertica agent API key, ensuring only authorized Vertica components and administrators can read it. Consult Vertica documentation or patches for version-specific permission guidance.

Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 12.0.4-30, 23.3.0-11, 23.4.0-13, 24.1.0-8, 24.2.0-4, or 24.3.0-1 (or later)

  1. 1. Identify the currently installed Vertica version using 'SELECT version();' or checking the installation directory
  2. 2. Determine which version range your current installation falls into (10.0.0-0 to 12.x, 23.0.x to 23.3.x, 23.4.x, 24.1.x, 24.2.x, or 24.3.0-0)
  3. 3. For version 10.x/11.x: Upgrade to Vertica 12.0.4-30 or later
  4. 4. For version 23.0.x to 23.3.x: Upgrade to Vertica 23.3.0-11 or later
  5. 5. For version 23.4.x: Upgrade to Vertica 23.4.0-13 or later
  6. 6. For version 24.1.x: Upgrade to Vertica 24.1.0-8 or later
  7. 7. For version 24.2.x: Upgrade to Vertica 24.2.0-4 or later
  8. 8. For version 24.3.0-0: Upgrade to Vertica 24.3.0-1 or later
Caveat Standard Vertica upgrade procedures apply; review upgrade documentation for your specific version jump for compatibility considerations and ensure proper backup before upgrading

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

Fix this in Vertica Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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