CVE-2023-44039
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 · uneditedIn VeridiumID before 3.5.0, the WebAuthn API allows an internal unauthenticated attacker (who can pass enrollment verifications and is allowed to enroll a FIDO key) to register their FIDO authenticator to a victim’s account and consequently take over the account.
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 confidenceIn VeridiumID before version 3.5.0, the WebAuthn enrollment API contains an authentication bypass allowing an unauthenticated internal attacker to register their FIDO authenticator to a victim's account by bypassing enrollment verification controls, enabling complete account takeover.
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< 3.5.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 VeridiumID versionLocate the VeridiumID installation and check the installed version number against the product documentation or use the product's admin console/system information to determine the running version.Affected if The installed version is lower than 3.5.0 (any version below 3.5.0 is affected).
-
Verify WebAuthn enrollment is enabledAccess the VeridiumID admin console or configuration settings and check whether the WebAuthn enrollment feature is turned on or available for user authentication.Affected if WebAuthn enrollment is enabled or configured as an authentication method.
-
Review registered WebAuthn credentialsCheck the user account management section in the VeridiumID admin console to list all registered WebAuthn authenticators for each user account.Affected if There are unexpected or unauthorized FIDO authenticator registrations, or the list shows credentials that users did not register themselves.
-
Inspect authentication audit logsReview the VeridiumID audit and authentication logs for enrollment events, focusing on WebAuthn registration attempts, especially those from internal network sources.Affected if There are WebAuthn enrollment events that show unauthenticated or unexpected requests, or registrations occurring without proper user verification.
The environment is affected if VeridiumID version is below 3.5.0 and WebAuthn enrollment is enabled, warranting a review of recent authenticator registrations for unauthorized 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.
dbcve · scoped3.5.0
Upgrade to VeridiumID 3.5.0 or later to remediate the WebAuthn enrollment bypass vulnerability.
3.5.0
- Identify the current VeridiumID version in use by checking the admin console or system inventory
- Review the VeridiumID upgrade documentation at docs.veridiumid.com for your deployment type
- Backup the current VeridiumID configuration and database
- Upgrade VeridiumID to version 3.5.0 or later following the official upgrade procedure
- Verify the WebAuthn authentication flow after upgrade to ensure the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44039 — 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-2023-44039 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