← Back to results
Vulnerability record · public intelligence
CVE-2024-28851
MEDIUM

Elevation of privilege in Snowflake Hive MetaStore Connector Helper script

Published Mar 15, 2024 · Updated Oct 23, 2026

Severity · CVSSMEDIUM · 4.0
Known exploitationNot listed
EPSS / likelihood0.25%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Elevation of privilege in Snowflake Hive MetaStore Connector Helper script

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

The Snowflake Hive metastore connector provides an easy way to query Hive-managed data via Snowflake. Snowflake Hive MetaStore Connector has addressed a potential elevation of privilege vulnerability in a `helper script` for the Hive MetaStore Connector. A malicious insider without admin privileges could, in theory, use the script to download content from a Microsoft domain to the local system and replace the valid content with malicious code. If the attacker then also had local access to the same system where the maliciously modified script is run, they could attempt to manipulate users into executing the attacker-controlled helper script, potentially gaining elevated privileges to the local system. The vulnerability in the script was patched on February 09, 2024, without a version bump to the Connector. User who use the helper script are strongly advised to use the latest version as soon as possible. Users unable to upgrade should avoid using the helper script.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Source repository ↗

Record history

Published Mar 15, 2024 · Last refreshed Oct 23, 2026