Cyber Resilience

CVE-2023-30970

Path Traversal in Palantir Gotham Blackbird-Witchcraft 10.1 – 104.30231001.8

Published
29 January 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0054 43th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2023-30970 is a medium-severity Absolute Path Traversal (CWE-36) vulnerability in Palantir Gotham Blackbird-Witchcraft. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Gotham Table service and Forward App were found to be vulnerable to a Path traversal issue allowing an authenticated user to read arbitrary files on the file system.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-7323Shared CWE-22, CWE-36
CVE-2024-29053Shared CWE-22, CWE-36
CVE-2026-42315Shared CWE-22, CWE-36
CVE-2024-1703Shared CWE-22, CWE-36
CVE-2023-34135Shared CWE-22, CWE-36
CVE-2024-8778Shared CWE-22, CWE-36
CVE-2024-20379Shared CWE-22, CWE-36
CVE-2018-20250Shared CWE-22, CWE-36
CVE-2025-15227Shared CWE-22, CWE-36
CVE-2023-40597Shared CWE-22, CWE-36

Affected Assets

palantir
gotham blackbird-witchcraft
10.1 — 104.30231001.8 · 10.2 — 104.30231002.10 · 10.3 — 104.30231003.9
palantir
gotham static-assets-servlet
≤ 1.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly stops construction of absolute paths from untrusted data before they reach file operations.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent absolute path traversal.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect absolute path traversal via static analysis and fuzzing.

prevents

Secure development lifecycle includes input validation and path-handling requirements that reduce absolute path traversal risk.

prevents

Application security requirements typically mandate controls against path traversal in file-access functions.

prevents

Secure architecture principles call for canonicalization and sandboxing that limit absolute path traversal.

prevents

Secure coding standards directly require neutralization of absolute path sequences in pathname construction.

mitigates

Information access restriction limits which files can be reached but does not address the path-construction flaw itself.

References