# CVE-2024-45674: IBM Security Verify Bridge information disclosure

> Local users can read sensitive information from log files in IBM Security Verify Bridge components, requiring a patch to mitigate.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 15 Aug 2025
- **Also known as:** GHSA-536f-wq7f-mx95

## What is CVE-2024-45674?

CVE-2024-45674 is a low-severity vulnerability in IBM Security Verify Bridge Directory Sync, published on 21 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Security Verify Bridge Directory Sync 1.0.1 through 1.0.12, IBM Security Verify Gateway for Windows Login 1.0.1 through 1.0.10, and IBM Security Verify Gateway for Radius 1.0.1 through 1.0.11 

stores potentially sensitive information in log files that could be read by a local user.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-45674?

It affects 3 products.


Products: Ibm Security Verify Bridge Directory Sync, Ibm Security Verify Gateway for Radius, Ibm Security Verify Gateway for Windows Login.

## How do I fix CVE-2024-45674?

No fix has been published for CVE-2024-45674 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45674 being exploited?

There is no known exploitation of CVE-2024-45674 in the wild and no public exploit code.

## Other vulnerabilities in IBM Security Verify Bridge Directory Sync

- [CVE-2024-45673](https://insights.sbomify.com/CVE-2024-45673/): IBM Security Verify Bridge information disclosure (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45674 and fix it if it is affected.

What it is: CVE-2024-45674 is a low-severity vulnerability in IBM Security Verify Bridge Directory Sync, published on 21 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45674 in the wild and no public exploit code.

Affected product: IBM Security Verify Bridge Directory Sync. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45674/ (Markdown: https://insights.sbomify.com/CVE-2024-45674/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45674
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45674
- OSV: https://osv.dev/vulnerability/CVE-2024-45674

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45674/
Summaries are generated and may contain mistakes; the official description above is the record.