dbcve.org
Security Verify AccessApplication · Ibm

CVE-2024-35133

HIGH · 8.2 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to after 10.0.8 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
IBM Security Verify Access 10.0.0 through 10.0.8 OIDC Provider could allow a remote authenticated attacker to conduct phishing attacks, using an open redirect attack. By persuading a victim to visit a specially crafted Web site, a remote attacker could exploit this vulnerability to spoof the URL displayed to redirect a user to a malicious Web site that would appear to be trusted. This could allow the attacker to obtain highly sensitive information or conduct further attacks against the victim.

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 confidence

IBM Security Verify Access 10.0.0-10.0.8 OIDC Provider contains an open redirect vulnerability where an authenticated attacker can craft malicious URLs that appear to originate from the legitimate Verify Access domain but redirect users to attacker-controlled malicious sites, enabling phishing attacks.

MitigationUpgrade IBM Security Verify Access to a version beyond 10.0.8 or implement strict URL validation/whitelist controls in the OIDC Provider configuration to prevent untrusted redirect destinations.

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
Security Verify AccessApplication
Affected:>= 10.0.0, <= 10.0.8
Security Verify Access DockerApplication
Affected:>= 10.0.0, <= 10.0.8

CVSS 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
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Security Verify Access installation
    Check for the product by searching for verify access installation directories (commonly /opt/IBM/verify or C:\Program Files\IBM\Verify) or running 'docker ps' to look for verify access container images
    Affected if IBM Security Verify Access or its Docker variant is present on the system
  2. Determine installed version
    Run the product version command (typically 'verify version' or check /opt/IBM/verify/access/versions.txt on Linux, or docker images to check the image tag version)
    Affected if The installed version falls within 10.0.0 through 10.0.8 inclusive
  3. Confirm OIDC Provider is configured
    Inspect the OIDC Provider configuration files in the verify access admin console or check for oidc configuration files in the configuration directory (typically under /var/Verify/oidc or the config/oidc path)
    Affected if OIDC Provider is enabled and configured with client registrations
  4. Check redirect URI validation settings
    Review the OIDC Provider client registration settings to see if redirect URIs are validated against a whitelist or if arbitrary external URLs are permitted
    Affected if The OIDC Provider allows redirect URIs to point to arbitrary external domains without strict validation or whitelist enforcement

You are affected if IBM Security Verify Access versions 10.0.0-10.0.8 are installed with OIDC Provider configured and redirect URI validation is not strictly enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 10.0.8
Interim mitigation

Upgrade IBM Security Verify Access to a version beyond 10.0.8 or implement strict URL validation/whitelist controls in the OIDC Provider configuration to prevent untrusted redirect destinations.

Recommended fix Moderate confidence

10.0.9 or later (10.0.x series)

  1. 1. Identify the current IBM Security Verify Access version in use by checking the administration console or using the 'docker ps' command for containerized deployments
  2. 2. Review the release notes for IBM Security Verify Access version 10.0.9 or later for security fixes addressing CVE-2024-35133
  3. 3. Plan an upgrade to a fixed version (10.0.9 or later) following IBM's standard upgrade procedure
  4. 4. Before upgrading in production, test the new version in a non-production environment to verify compatibility with existing configurations
  5. 5. Backup the current configuration before performing the upgrade
  6. 6. Execute the upgrade process according to IBM's official documentation for your deployment type (traditional or Docker)
  7. 7. After upgrade, verify the OIDC Provider configuration and test that open redirect protections are functioning
  8. 8. Monitor for any anomalous redirects or phishing attempts in logs post-upgrade
Caveat Review IBM release notes for any configuration or behavioral changes between 10.0.8 and the target fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Verify Access Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35133 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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