CVE-2023-30970
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 · uneditedGotham 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.
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 confidencePath traversal vulnerability in Gotham Table service and Forward App allows authenticated users to read arbitrary files on the filesystem by manipulating file path parameters with traversal sequences (e.g., ../../).
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>= 10.1, < 104.30231001.8>= 10.2, < 104.30231002.10>= 10.3, < 104.30231003.9>= 9.8, < 104.30230908.21>= 8.7, < 104.30230807.59>= 6.4, < 104.30230604.81>= 3.4, < 103.30230304.433< 1.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Gotham platform versionLocate the installed Palantir Gotham version using the platform's version reporting mechanism (typically via admin console, version file, or system information command)Affected if The installed version falls into any of these ranges: >= 10.1 and < 104.30231001.8; >= 10.2 and < 104.30231002.10; >= 10.3 and < 104.30231003.9; >= 9.8 and < 104.30230908.21; >= 8.7 and < 104.30230807.59; >= 6.4 and < 104.30230604.81; >= 3.4 and < 103.30230304.433
-
Confirm Gotham Table service is activeCheck if the Gotham Table service module is enabled and accessible in the deploymentAffected if The Table service is running and accepts file path parameters from authenticated users
-
Check Forward App module statusVerify whether the Forward App component is enabled and exposedAffected if Forward App is accessible to authenticated users and handles file request parameters
-
Identify Static Assets Servlet versionLocate the version of the Gotham Static Assets Servlet component if deployedAffected if Static Assets Servlet version is less than 1.1.0
The environment is affected if Gotham or Static Assets Servlet version falls within the affected ranges AND the Table service or Forward App is accessible to authenticated users.
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 data1.1.0103.30230304.433104.30230604.81
Implement strict input validation and path sanitization for all file access operations, ensuring paths are canonicalized and confined to allowed directories to prevent traversal sequences.
- 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-2023-30970 — 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-2023-30970 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