CVE-2023-30948
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 · uneditedA security defect in Foundry's Comments functionality resulted in the retrieval of attachments to comments not being gated by additional authorization checks. This could enable an authenticated user to inject a prior discovered attachment UUID into other arbitrary comments to discover it's content. This defect was fixed in Foundry Comments 2.249.0, and a patch was rolled out to affected Foundry environments. No further intervention is required at this time.
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 confidenceInsecure direct object reference (IDOR) in Foundry's Comments functionality where attachment retrieval lacks proper authorization checks, allowing authenticated users to access attachments from arbitrary comments by manipulating attachment UUIDs.
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< 2.249.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 Foundry Comments versionAccess the Foundry admin console or check the installed Palantir Foundry platform version details. Navigate to Platform Settings > System Information or check the installed packages/configuration files for the Comments module version.Affected if The installed Foundry Comments version is below 2.249.0 (e.g., 2.248.x, 2.247.x, etc.)
-
Verify Comments module is enabledCheck the Foundry platform configuration to confirm the Comments functionality is active. Look in the platform admin settings under Modules or Feature Flags for the Comments service.Affected if The Comments module is enabled and accessible to authenticated users in the environment
-
Confirm user access to attachment functionalityExamine user role permissions within Foundry to determine if standard authenticated users have access to create or view comments with attachments. Check Identity & Access Management settings.Affected if Authenticated users have permissions to use the Comments feature with attachment capabilities
-
Test attachment retrieval authorizationUsing an authenticated user account, attempt to access a comment attachment, then manually construct a request using a different attachment UUID from another comment to see if unauthorized access is possible (requires two different comment attachments exist).Affected if A user can retrieve attachments from comments they did not create by manipulating the attachment UUID parameter
The environment is affected if Foundry Comments version is below 2.249.0 AND the Comments module with attachment functionality is enabled for 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.
dbcve · scoped2.249.0
Vendor reports patch was already deployed in Foundry Comments 2.249.0; verify environment is on current version and conduct access control validation testing.
- No further action required. The vulnerability has already been addressed through a patch that was rolled out to affected Foundry environments.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30948 — 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-30948 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