CVE-2024-45647
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 Access 10.0.0 through 10.0.8 and IBM Security Verify Access Docker 10.0.0 through 10.0.8 could allow could an unverified user to change the password of an expired user without prior knowledge of that password.
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 Access 10.0.0 through 10.0.8 contains an authentication bypass vulnerability where an unverified (unauthenticated) user can change the password of an expired account without any prior knowledge of the original password. This allows full account takeover of expired users.
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>= 10.0.0, <= 10.0.8>= 10.0.0, <= 10.0.8CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Security Verify Access versionRun 'docker ps' if using Docker, or check the product version via the admin console or command line interface using 'isva --version' or check /opt/ibm/verifyaut/version.propertiesAffected if Installed version is 10.0.0 through 10.0.8 inclusive
-
Confirm password change endpoint is accessibleCheck if the password reset/change endpoint accepts requests without prior authentication. This typically involves reviewing the web server configuration or API gateway settings for the /mga/sps/apiauthsvc endpoint.Affected if The password change API endpoint is exposed and accepts requests without valid session authentication
-
Review authentication logs for password change attemptsExamine authentication logs in /var/log/isva/audit or via the admin console for failed password change attempts on expired accounts. Look for entries with 'password change' or 'password reset' where the user status is 'expired'.Affected if Logs show password change attempts on expired accounts that succeeded without proper original password verification
-
Check for unauthorized password changes on expired accountsQuery the user directory or identity store for accounts with status 'expired' that have recent password modification timestamps. Use LDAP queries or the admin API to list user account statuses and last password change dates.Affected if Expired user accounts have recent password change timestamps that were not initiated by legitimate users
A system is affected if it runs IBM Security Verify Access version 10.0.0-10.0.8 and has the password change endpoint accessible to unauthenticated users, allowing password resets on expired accounts.
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.
dbcve · scopedUpgrade IBM Security Verify Access (both base and Docker variants) to version 10.0.9 or later. If immediate upgrade is not feasible, review and restrict network access to the authentication endpoints.
IBM Security Verify Access 10.0.9 or later / Security Verify Access Docker 10.0.9 or later
- Verify current IBM Security Verify Access version by checking the administration console or using the 'docker ps' command for Docker deployments
- For on-premise deployments: Back up current configuration and user data before upgrade
- For Docker deployments: Pull the latest available IBM Security Verify Access Docker image from IBM's container registry
- Upgrade to IBM Security Verify Access version 10.0.9 or later (or the latest stable release)
- After upgrade, verify that the password change functionality now properly validates user credentials before allowing password modifications
- Test the fix by attempting to change an expired user's password without proper authentication to confirm the vulnerability is resolved
- Review IBM Security Verify Access logs to ensure no unauthorized password changes occurred prior to the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45647 — 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-45647 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