CVE-2024-45673
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 · uneditedIBM 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 user credentials in configuration files which can be read by a local user.
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 confidenceIBM Security Verify products (Bridge Directory Sync, Gateway for Windows Login, and Gateway for Radius) store user credentials in plaintext within configuration files. Local users with access to the system can read these configuration files and obtain stored credentials, leading to unauthorized access or privilege escalation.
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>= 1.0.1, <= 1.0.12>= 1.0.1, <= 1.0.11>= 1.0.1, <= 1.0.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Security Verify productList installed programs or services on the system to determine if any of these products are present: Bridge Directory Sync, Gateway for Radius, or Gateway for Windows LoginAffected if Any of the three affected products is installed on the system
-
Check installed product versionUse system utilities (such as program properties, installed packages list, or product-specific version command) to determine the exact version of the installed IBM Security Verify productAffected if The version falls within the affected range: Bridge Directory Sync 1.0.1-1.0.12, Gateway for Radius 1.0.1-1.0.11, or Gateway for Windows Login 1.0.1-1.0.10
-
Locate configuration filesSearch for configuration files associated with the installed product, typically found in installation directories, config subfolders, or application data locationsAffected if Configuration files exist for the installed product
-
Inspect configuration files for plaintext credentialsOpen and examine the contents of configuration files for patterns indicating stored credentials such as password, username, secret, or credential fields with unobfuscated valuesAffected if Configuration files contain username, password, secret, or other credential values stored in plaintext (readable, unencrypted format)
The environment is affected if any IBM Security Verify product (Bridge Directory Sync, Gateway for Radius, or Gateway for Windows Login) is installed with a version within the specified ranges AND configuration files contain plaintext credentials.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict file system permissions on configuration files to prevent unauthorized local access, migrate credentials to a secure credential storage mechanism (e.g., Windows Credential Manager, encrypted secrets vault), and rotate any credentials that may have been exposed.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45673 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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