Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-45674: IBM Security Verify Bridge Directory Sync 1.0.1 through 1.0.12, IBM Security Verify Gateway for Windows Login

13
Routine
LOW 3.3UPGRADEUPGRADEUPGRADE

CVE-2024-45674 is a low-severity flaw (CVSS 3.3) affecting security verify bridge directory sync, security verify gateway for radius, security verify gateway for windows login. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score3.3 (Low)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 95%)
CISA exploited listNo
WeaknessCWE-532
Published2025-02-22
Last modified2026-06-17
Publisher (CNA): IBM Corporation · Vendor: ibm

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

ibm security verify bridge directory sync UPGRADE
Affected: >= 1.0.1 and <= 1.0.12
Fixed in: newer than 1.0.12
Safe to downgrade to: a release before 1.0.1
1. Check installed version
apt-cache policy security-verify-bridge-directory-sync || rpm -q security-verify-bridge-directory-sync || security-verify-bridge-directory-sync --version
2. UPGRADE to newer than 1.0.12 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade security-verify-bridge-directory-sync
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade security-verify-bridge-directory-sync
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.1 (Debian / Ubuntu)
apt-cache madison security-verify-bridge-directory-sync sudo apt install security-verify-bridge-directory-sync=<VERSION_BEFORE_1.0.1> sudo apt-mark hold security-verify-bridge-directory-sync
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list security-verify-bridge-directory-sync sudo dnf downgrade security-verify-bridge-directory-sync-<VERSION_BEFORE_1.0.1> sudo dnf versionlock add security-verify-bridge-directory-sync
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ibm security verify gateway for radius UPGRADE
Affected: >= 1.0.1 and <= 1.0.11
Fixed in: newer than 1.0.11
Safe to downgrade to: a release before 1.0.1
1. Check installed version
apt-cache policy security-verify-gateway-for-radius || rpm -q security-verify-gateway-for-radius || security-verify-gateway-for-radius --version
2. UPGRADE to newer than 1.0.11 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade security-verify-gateway-for-radius
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade security-verify-gateway-for-radius
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.1 (Debian / Ubuntu)
apt-cache madison security-verify-gateway-for-radius sudo apt install security-verify-gateway-for-radius=<VERSION_BEFORE_1.0.1> sudo apt-mark hold security-verify-gateway-for-radius
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list security-verify-gateway-for-radius sudo dnf downgrade security-verify-gateway-for-radius-<VERSION_BEFORE_1.0.1> sudo dnf versionlock add security-verify-gateway-for-radius
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ibm security verify gateway for windows login UPGRADE
Affected: >= 1.0.1 and <= 1.0.10
Fixed in: newer than 1.0.10
Safe to downgrade to: a release before 1.0.1
1. Check installed version
apt-cache policy security-verify-gateway-for-windows-login || rpm -q security-verify-gateway-for-windows-login || security-verify-gateway-for-windows-login --version
2. UPGRADE to newer than 1.0.10 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade security-verify-gateway-for-windows-login
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade security-verify-gateway-for-windows-login
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.1 (Debian / Ubuntu)
apt-cache madison security-verify-gateway-for-windows-login sudo apt install security-verify-gateway-for-windows-login=<VERSION_BEFORE_1.0.1> sudo apt-mark hold security-verify-gateway-for-windows-login
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list security-verify-gateway-for-windows-login sudo dnf downgrade security-verify-gateway-for-windows-login-<VERSION_BEFORE_1.0.1> sudo dnf versionlock add security-verify-gateway-for-windows-login
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-45674?

security verify bridge directory sync: upgrade to newer than 1.0.12; security verify gateway for radius: upgrade to newer than 1.0.11; security verify gateway for windows login: upgrade to newer than 1.0.10. Exact commands for each OS are on this page.

Is CVE-2024-45674 being exploited?

CVE-2024-45674 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-45674 affect?

CVE-2024-45674 affects security verify bridge directory sync, security verify gateway for radius, security verify gateway for windows login. Severity is low (CVSS 3.3). 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 i

How urgent is CVE-2024-45674?

Priority 13/100. No elevated risk signals yet.

Software pages

Windows vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.