CVE-2023-30950
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 · uneditedThe foundry campaigns service was found to be vulnerable to an unauthenticated information disclosure in a rest endpoint
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 confidenceThe foundry campaigns service contains a REST endpoint that exposes sensitive information to unauthenticated users. An attacker can access this endpoint without any authentication credentials to retrieve potentially confidential data.
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< 0.623.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/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 if Foundry Campaigns is deployedLocate the Palantir Foundry Campaigns service in your environment. Check for processes, containers, or services running the Foundry Campaigns component.Affected if Foundry Campaigns service is present in the environment
-
Check installed Foundry Campaigns versionRetrieve the version number of the installed Foundry Campaigns service using your system's package manager, service diagnostics, or administration console. Compare the version against the affected range: versions prior to 0.623.0.Affected if The installed version is lower than 0.623.0
-
Identify the vulnerable REST endpointConsult Foundry Campaigns documentation or network traffic analysis to locate REST endpoints that handle sensitive data operations. The vulnerability affects endpoints that should require authentication.Affected if A REST endpoint handling sensitive data is exposed by the service
-
Test endpoint access without authenticationAttempt to access the identified REST endpoint using HTTP requests without providing any authentication credentials (no API keys, tokens, or session cookies). Observe whether the request succeeds and returns data.Affected if The endpoint returns successful HTTP responses and sensitive data without requiring authentication credentials
-
Verify sensitive data exposureExamine the response from the unauthenticated endpoint request. Check if the returned data contains confidential information such as user data, campaign metrics, or other sensitive content.Affected if The endpoint returns sensitive or confidential data to unauthenticated requests
Your environment is affected if Foundry Campaigns version is below 0.623.0 AND the service exposes a REST endpoint that returns sensitive data to requests without authentication credentials.
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 · scoped0.623.0
Implement authentication and authorization controls on the vulnerable REST endpoint to ensure only authorized users can access sensitive data.
0.623.0
- Verify current Foundry Campaigns version in use
- Plan maintenance window for upgrade
- Back up current configuration and data
- Upgrade Foundry Campaigns to version 0.623.0 or later
- Verify the upgrade was successful
- Test that the unauthenticated endpoint is now properly secured
- Monitor for any post-upgrade issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30950 — 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-30950 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