dbcve.org
Clips2Application · Palantir

CVE-2023-30945

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-26
Fix available
A fix is available. Upgrade to 0.24.10 / 0.111.2 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
Multiple Services such as VHS(Video History Server) and VCD(Video Clip Distributor) and Clips2 were discovered to be vulnerable to an unauthenticated arbitrary file read/write vulnerability due to missing input validation on filenames. A malicious attacker could read sensitive files from the filesystem or write/delete arbitrary files on the filesystem as well.

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

Multiple video services (VHS, VCD, Clips2) contain an unauthenticated arbitrary file read/write vulnerability due to missing input validation on filenames. Attackers can read sensitive system files or write/delete arbitrary files by supplying specially crafted file paths without proper sanitization.

MitigationImplement strict input validation and path sanitization for all file operations, using allowlist approaches and preventing path traversal sequences (../) to restrict access to intended directories only.

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
Clips2Application
Affected:< 0.111.2
Video Clip DistributorApplication
Affected:< 0.24.10
Video History ServiceApplication
Affected:< 2.210.3

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 Palantir video service
    Search for running processes or installed packages named 'clips2', 'video-clip-distributor', 'video-history-service', 'vcd', or 'vhs'. Check service logs or system inventory for these components.
    Affected if Any of these Palantir video services are installed and running
  2. Check installed version of Clips2
    Run command to retrieve Clips2 version (e.g., 'clips2 --version', check manifest file, or query the service's /version endpoint if exposed). Compare the version number against 0.111.2.
    Affected if Version is lower than 0.111.2
  3. Check installed version of Video Clip Distributor
    Run command to retrieve VCD version (e.g., 'vcd --version', check manifest file, or query the service's /version endpoint if exposed). Compare the version number against 0.24.10.
    Affected if Version is lower than 0.24.10
  4. Check installed version of Video History Service
    Run command to retrieve VHS version (e.g., 'vhs --version', check manifest file, or query the service's /version endpoint if exposed). Compare the version number against 2.210.3.
    Affected if Version is lower than 2.210.3
  5. Verify if file operation endpoints are accessible
    Check if the web API or HTTP endpoints for file operations (file upload, download, clip retrieval) are exposed without authentication. Review network configuration and service ACLs.
    Affected if File operation endpoints are reachable without authentication

A user is affected if any Palantir Clips2 (< 0.111.2), Video Clip Distributor (< 0.24.10), or Video History Service (< 2.210.3) is running with unauthenticated file operation endpoints exposed.

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 0.24.10 / 0.111.2 / 2.210.3 or later
Fixed in 0.24.100.111.22.210.3
Interim mitigation

Implement strict input validation and path sanitization for all file operations, using allowlist approaches and preventing path traversal sequences (../) to restrict access to intended directories only.

Recommended fix High confidence

Clips2: 0.111.2 | Video Clip Distributor: 0.24.10 | Video History Service: 2.210.3

  1. Identify which of the affected services (Clips2, Video Clip Distributor, Video History Service) are deployed in your environment
  2. For Clips2: Upgrade to version 0.111.2 or later
  3. For Video Clip Distributor: Upgrade to version 0.24.10 or later
  4. For Video History Service: Upgrade to version 2.210.3 or later
  5. After upgrading, verify that the path traversal vulnerability is remediated by testing file access controls
  6. Ensure proper input validation is in place for filename parameters in your deployment

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

Fix this in Clips2 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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