dbcve.org
Security Verify AccessApplication · Ibm

CVE-2024-31883

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-27
Fix available
A fix is available. Upgrade to after 10.0.7.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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.0 through 10.0.7.1, under certain configurations, could allow an unauthenticated attacker to cause a denial of service due to asymmetric resource consumption. IBM X-Force ID: 287615.

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 confidence

IBM Security Verify Access versions 10.0.0.0 through 10.0.7.1 contains a denial of service vulnerability where unauthenticated attackers can exploit asymmetric resource consumption under certain configurations. This type of flaw typically involves sending small requests that trigger disproportionate server-side resource usage (such as hash collision attacks or similar algorithmic complexity exploits), causing the service to become unavailable.

MitigationIdentify and modify the vulnerable configurations referenced in the advisory, and apply available vendor patches to upgrade beyond version 10.0.7.1. Consider implementing rate limiting or request throttling as an interim compensating control.

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.0, <= 10.0.7.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Confirm IBM Security Verify Access is installed
    Locate the IBM Security Verify Access installation directory or check installed packages using system inventory tools (e.g., 'dpkg -l', 'rpm -qa', or Windows Programs and Features)
    Affected if The product is present on the system
  2. Check installed version against affected range
    Run 'amversion' or check /opt/IBM/verity/am/bin version information, or use 'docker ps' for containerized deployments
    Affected if The installed version is 10.0.0.0 through 10.0.7.1 inclusive
  3. Review configuration for unauthenticated request handling
    Examine the Verify Access configuration files (typically in /var/IBM/verity/am/config or equivalent) for settings related to unauthenticated endpoint exposure
    Affected if Unauthenticated endpoints are exposed without request throttling or rate limiting configured
  4. Identify resource consumption controls
    Check whether algorithmic complexity protections such as request rate limiting, hash collision mitigations, or request size limits are enabled in the appliance or container configuration
    Affected if Rate limiting or resource consumption controls are not implemented for unauthenticated requests

A user is affected if IBM Security Verify Access version 10.0.0.0 through 10.0.7.1 is installed with configurations that allow unauthenticated requests without adequate resource consumption controls.

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.7.1
Interim mitigation

Identify and modify the vulnerable configurations referenced in the advisory, and apply available vendor patches to upgrade beyond version 10.0.7.1. Consider implementing rate limiting or request throttling as an interim compensating control.

Recommended fix Moderate confidence

10.0.8.0 or later

  1. 1. Review the current IBM Security Verify Access deployment and confirm the installed version (10.0.0.0 through 10.0.7.1).
  2. 2. Schedule a maintenance window for the upgrade process.
  3. 3. Back up the current IBM Security Verify Access configuration and data.
  4. 4. Download IBM Security Verify Access version 10.0.8.0 or later from IBM Fix Central or the IBM Passport Advantage site.
  5. 5. Follow the IBM upgrade documentation to install the new version, ensuring all prerequisites are met.
  6. 6. After upgrade, verify that the Security Verify Access services start correctly.
  7. 7. Test that the appliance is functioning properly and accessible.
  8. 8. Validate that the vulnerability is remediated by reviewing system logs for any resource consumption anomalies.
Caveat Review IBM release notes for 10.0.8.0 for any configuration or behavioral changes that may affect your deployment

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

Fix this in Security Verify Access Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31883 — 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-31883 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