CVE-2015-6867
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 · uneditedThe vertica-udx-zygote process in HP Vertica 7.1.1 UDx does not require authentication, which allows remote attackers to execute arbitrary commands via a crafted packet, aka ZDI-CAN-2914.
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 confidenceHP Vertica 7.1.1 contains an authentication bypass vulnerability in the vertica-udx-zygote process (User-Defined Extensions). The process does not require authentication, allowing remote unauthenticated attackers to send specially crafted packets and execute arbitrary commands on the affected system with the privileges of the vertica user.
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= 7.1.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Vertica versionRun 'SELECT VERSION();' in vsql or check the /opt/vertica/bin/vertica version outputAffected if The version is exactly 7.1.1
-
Verify if the vertica-udx-zygote process is runningCheck running processes for vertica-udx-zygote using 'ps aux | grep vertica-udx-zygote' or check process list via system monitoring toolsAffected if The process is active and accepting connections
-
Determine if the vertica-udx-zygote service is network accessibleReview firewall rules and network configuration to see if the vertica-udx-zygote port is exposed to untrusted networks. Check listening ports with 'netstat -anp | grep vertica-udx-zygote' or similar tool.Affected if The service is bound to a network interface accessible from untrusted hosts
-
Confirm User-Defined Extensions (UDX) feature is enabledCheck if UDx functions are deployed or if the UDX framework is active by querying the user_functions system table or reviewing UDF deployment configurationAffected if UDX is enabled and the vertica-udx-zygote process handles these requests without authentication
A system is affected if it runs Vertica version 7.1.1 with the vertica-udx-zygote process exposed to the network and UDX feature enabled, allowing unauthenticated remote command execution.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade HP Vertica to version 7.2 or later which contains the patch for this vulnerability. If immediate patching is not possible, restrict network access to the vertica-udx-zygote port using firewall rules or network segmentation to limit exposure to trusted hosts only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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