dbcve.org
Security Verify BridgeApplication · Ibm

CVE-2024-45672

MEDIUM · 6.0 CVSS v3.1 Published 2025-01-23
Fix available
A fix is available. Upgrade to 1.0.16 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Bridge 1.0.0 through 1.0.15 could allow a local privileged user to overwrite files due to excessive privileges granted to the agent. which could also cause a denial of service.

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 Bridge versions 1.0.0-1.0.15 grants excessive file system privileges to its agent component, allowing a local privileged user to overwrite arbitrary files on the system. This privilege escalation vulnerability could enable code execution via file replacement or cause denial of service by overwriting critical system files.

MitigationUpgrade to IBM Security Verify Bridge version 1.0.16 or later, which addresses the excessive privilege issue. Alternatively, restrict file system permissions for the agent service account to prevent arbitrary file overwrites.

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 BridgeApplication
Affected:>= 1.0.0, < 1.0.16

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/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. Verify IBM Security Verify Bridge is installed
    Check for the presence of IBM Security Verify Bridge installation directory (commonly under C:\Program Files\IBM\Verify Bridge on Windows or /opt/ibm/verify-bridge on Linux). Also check running services for 'IBM Security Verify Bridge' or 'ISVB' processes.
    Affected if IBM Security Verify Bridge is found on the system
  2. Identify installed version
    Locate the version file or executable. On Windows, check the file properties of the installed executable or check the registry under HKLM\SOFTWARE\IBM\Security Verify Bridge. On Linux, run: rpm -q ibm-security-verify-bridge or check /opt/ibm/verify-bridge/version
    Affected if Version cannot be determined or is 1.0.0 through 1.0.15 inclusive
  3. Confirm version falls within affected range
    Compare your identified version against the vulnerable range: versions 1.0.0 through 1.0.15 are affected. Version 1.0.16 and later are fixed.
    Affected if Installed version is 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.14, or 1.0.15
  4. Check agent component service account permissions
    Identify the service account running the IBM Security Verify Bridge agent service. On Windows, use Services.msc and check the Log On As account. On Linux, check the service configuration or process owner (ps aux | grep verify-bridge).
    Affected if Agent runs with elevated privileges that allow write access to arbitrary file system locations beyond its intended working directory

The environment is affected if IBM Security Verify Bridge versions 1.0.0 through 1.0.15 are installed and the agent component runs with elevated file system privileges.

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 1.0.16 or later
Fixed in 1.0.16
Interim mitigation

Upgrade to IBM Security Verify Bridge version 1.0.16 or later, which addresses the excessive privilege issue. Alternatively, restrict file system permissions for the agent service account to prevent arbitrary file overwrites.

Recommended fix High confidence

1.0.16

  1. Review the IBM Security Verify Bridge 1.0.16 release notes to understand changes and confirm the fix for CVE-2024-45672
  2. Backup the current IBM Security Verify Bridge configuration and data
  3. Test the upgrade in a non-production environment to verify compatibility
  4. Apply the upgrade to production systems following IBM's standard upgrade procedure
  5. Verify the installation and confirm the version is 1.0.16 or later
Caveat Review IBM documentation for any configuration changes required between 1.0.x versions

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

Fix this in Security Verify Bridge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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