CVE-2024-13966
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 · uneditedZKTeco BioTime allows unauthenticated attackers to enumerate usernames and log in as any user with a password unchanged from the default value '123456'. Users should change their passwords (located under the Attendance Settings tab as "Self-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 confidenceZKTeco BioTime contains an authentication vulnerability allowing unauthenticated attackers to enumerate valid usernames through login responses or API endpoints, then authenticate using any user account that still has the default password '123456'. This is a classic default credential vulnerability combined with user enumeration.
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< 9.0.4CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Determine BioTime versionAccess the BioTime admin interface or check system information to identify the currently installed version number.Affected if The installed version is below 9.0.4
-
Identify login interface exposureDetermine if the BioTime web login page or API endpoints are accessible from untrusted networks without authentication barriers.Affected if Login interface is exposed to unauthenticated access
-
Test for username enumerationSubmit login requests with different usernames and observe the response differences - particularly whether the system returns distinct error messages for valid versus invalid usernames.Affected if The system reveals whether a username exists through different error messages or response timing
-
Verify default password susceptibilityAttempt to authenticate using known valid usernames with the default password '123456'.Affected if Any user account can be accessed using '123456' as the password
-
Check for account lockout protectionSubmit multiple failed authentication attempts with different usernames and observe if the system implements account lockout or rate limiting.Affected if No account lockout or rate limiting is enforced, allowing unlimited login attempts
A user is affected if BioTime version is below 9.0.4 AND the login interface is externally accessible AND any user account still uses the default password '123456'.
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 · scoped9.0.4
Identify all BioTime user accounts with default passwords and enforce password changes through the Attendance Settings > Self-Password menu. Consider implementing account lockout policies and monitoring for brute-force enumeration attempts.
9.0.4
- Access the BioTime web interface
- Navigate to the Attendance Settings tab
- Locate the "Self-Password" setting for each user account
- Change the default password '123456' to a strong, unique password
- Verify the new password works by logging out and logging back in
- Repeat for all user accounts, especially administrative accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13966 — 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-13966 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