CVE-2024-35151
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 · uneditedIBM OpenPages with Watson 8.3 and 9.0 could allow authenticated users access to sensitive information through improper authorization controls on APIs.
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 confidenceIBM OpenPages with Watson versions 8.3 and 9.0 contains improper authorization controls on APIs, allowing authenticated users to access sensitive information beyond their intended permissions. This is a broken access control vulnerability where API endpoints fail to properly validate user authorization before returning 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= 8.3= 9.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 the IBM OpenPages versionCheck the installed version of IBM OpenPages or OpenPages with Watson in your environment. This is typically visible in the IBM OpenPages admin console under 'System' > 'Version Information', or by querying the OpenPages system information API if accessible.Affected if The installed version is 8.3 or 9.0 exactly.
-
Review API endpoint access controlsExamine the API configuration files and settings within the OpenPages administration interface. Look for API security configurations that control which endpoints are accessible and what authorization is required for each.Affected if API endpoints are exposed without proper role-based access control (RBAC) validation or if anonymous/unauthenticated access to sensitive API endpoints is allowed.
-
Audit user role assignments and data access permissionsReview the user role mappings in OpenPages GRC Platform. Check if users have been assigned roles that properly restrict their access to only the data domains they are authorized to view. Inspect role-to-data-scope mappings.Affected if Users with limited roles can potentially query API endpoints that return data outside their assigned permission scope.
-
Verify API authorization validation is enforcedTest API endpoints using an authenticated user account with restricted permissions. Attempt to access API resources or data objects outside the user's assigned role scope and observe whether the system properly denies access.Affected if The API returns data or allows access to resources that the authenticated user should not have permission to view based on their assigned role.
You are affected if you are running IBM OpenPages version 8.3 or 9.0 and your API endpoints allow authenticated users to access data beyond their assigned role permissions.
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 dataApply IBM security patches for OpenPages. Review and enforce proper authorization checks on all API endpoints to ensure users can only access data within their permitted scope.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35151 — 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-2024-35151 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