CVE-2024-35138
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 Security Verify Access Appliance and Container 10.0.0 through 10.0.8 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.
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 Security Verify Access Appliance and Container versions 10.0.0 through 10.0.8 contains a cross-site request forgery (CSRF) vulnerability. An attacker could craft malicious requests that trick authenticated users into unknowingly performing unauthorized actions on the appliance, leveraging the trust relationship between the user's browser and the server.
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.0.0, <= 10.0.8CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 installed versionLocate the IBM Security Verify Access version through the appliance admin console, command-line interface, or API endpointAffected if The installed version is 10.0.0 through 10.0.8 inclusive
-
Verify CSRF token implementationInspect the web application forms and API endpoints to determine whether anti-CSRF tokens are present on state-changing operationsAffected if Anti-CSRF tokens are missing or not validated on sensitive actions
-
Check cookie SameSite attributesExamine the session cookies emitted by the application using browser developer tools or HTTP traffic inspection to verify SameSite attribute configurationAffected if SameSite attribute is not set to 'Strict' or 'Lax' on session cookies
-
Validate Origin/Referer header checksReview server-side request validation logic to confirm Origin and Referer headers are checked before processing state-changing requestsAffected if Origin and Referer headers are not validated or enforced
You are affected if your IBM Security Verify Access version is between 10.0.0 and 10.0.8 inclusive AND CSRF protections (tokens, SameSite cookies, or Origin/Referer validation) are not properly implemented.
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 · scopedImplement anti-CSRF tokens on state-changing operations, configure SameSite cookie attributes, and validate Origin/Referer headers to prevent cross-site request forgery attacks.
10.0.9 or later (verify latest available version from IBM)
- 1. Review IBM Security Verify Access release notes and documentation at www.ibm.com for the latest available version
- 2. Plan an upgrade to a version beyond 10.0.8 (such as 10.0.9 or later)
- 3. Before upgrading in production, test the new version in a non-production environment
- 4. Perform a full backup of the current configuration
- 5. Execute the upgrade following IBM's documented upgrade procedure
- 6. After upgrade, verify that the web interface is accessible and all services are running
- 7. Test critical functions to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35138 — 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-35138 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