CVE-2021-35961
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 · uneditedDr. ID Door Access Control and Personnel Attendance Management system uses the hard-code admin default credentials that allows remote attackers to access the system through the default password and obtain the highest permission.
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 confidenceThe Dr. ID Door Access Control and Personnel Attendance Management system contains hard-coded default administrative credentials embedded in the application. Attackers can remotely authenticate using these default credentials to gain full administrative access to the system, enabling complete control over door access and personnel attendance records.
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.4.0.0.3.12_20210525CVSS 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 the installed version of Secom Dr.id Access ControlCheck the application's web interface footer, About page, or system information section for the exact version number. If you have access to the server, also check any version file in the application installation directory.Affected if The installed version is lower than 3.4.0.0.3.12_20210525
-
Verify default administrative credentials have been changedAttempt to log into the Dr.id administrative web interface using the default credentials (consult product documentation for the hardcoded default username/password combination, typically admin/admin or similar common defaults). If authentication succeeds, the credentials have not been changed.Affected if Default credentials still work and grant administrative access
-
Confirm the admin interface is not exposed to unauthenticated or untrusted networksReview firewall rules and network access controls to determine if the Dr.id administrative web portal is accessible from external networks, the internet, or untrusted internal segments. Use a network scanner to verify which IP ranges can reach port 443 or 80 on the Dr.id server.Affected if The administrative interface is accessible from untrusted networks without VPN or additional authentication
-
Audit existing administrative accounts for unauthorized additionsLog into the Dr.id administration panel and review the list of user accounts with administrative privileges. Compare against known, documented admin accounts created by your organization.Affected if Additional or unknown administrative accounts exist that were not created by your organization
You are affected if the installed version is below 3.4.0.0.3.12_20210525 AND default credentials remain unchanged, especially if the admin interface is network-accessible.
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.4.0.0.3.12_20210525
Immediately change the default administrative password to a strong, unique credential and disable or remove any unused default accounts. Implement a credential management process to prevent reuse of credentials across systems.
3.4.0.0.3.12_20210525 or later
- 1. Back up the current Dr.id Access Control system configuration and database before upgrading.
- 2. Obtain the fixed version (3.4.0.0.3.12_20210525 or later) from the official Dr.id vendor or authorized distribution channel.
- 3. Follow the vendor's documented upgrade procedure to install the new version.
- 4. After upgrade, immediately change the default admin password to a strong, unique password.
- 5. Verify the system is functioning correctly and the hard-coded credential vulnerability is resolved.
- 6. Consider implementing additional access controls such as IP whitelisting or two-factor authentication.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35961 — 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-2021-35961 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