CVE-2021-35962
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 · uneditedSpecific page parameters in Dr. ID Door Access Control and Personnel Attendance Management system does not filter special characters. Remote attackers can apply Path Traversal means to download credential files from the system without 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 · moderate confidenceThis is a path traversal vulnerability in Dr. ID Door Access Control and Personnel Attendance Management system where specific page parameters fail to filter special characters. Remote unauthenticated attackers can manipulate parameters to traverse directories and download sensitive credential files from the server.
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.3.2<= 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 version of Secom Door Access ControlCheck the application's about page, system info, or version file typically found in the web interface or installation directory. Look for version metadata in the application header or footer.Affected if Version number is 3.3.2 or lower
-
Identify installed version of Secom Personnel Attendance SystemAccess the application's system settings or administration panel to view the software version information, typically displayed in the help or about section.Affected if Version is 3.4.0.0.3.12_20210525 or lower
-
Determine if web interface is externally accessibleReview firewall rules, network configuration, and web server bindings to check if the Dr. ID application web portals are reachable from untrusted networks.Affected if The web interface is exposed to unauthenticated remote access
-
Locate credential or configuration filesSearch the application directory for configuration files containing database credentials, API keys, or system passwords. These are often stored in config folders, XML files, or encrypted credential stores.Affected if Credential files exist in accessible locations within the web root or application directories
-
Test for path traversal on vulnerable parametersUsing a web proxy or curl, attempt to access files outside the web root by manipulating URL parameters with patterns such as ../../../../etc/passwd or similar directory traversal sequences on the affected application pages.Affected if The application accepts and processes directory traversal sequences without proper validation, allowing unauthorized file access
You are affected if you are running Secom Door Access Control <= 3.3.2 or Secom Personnel Attendance System <= 3.4.0.0.3.12_20210525 with the web interface exposed to untrusted networks and vulnerable parameters accessible without authentication.
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 dataImplement strict input validation on all page parameters to reject directory traversal characters (.., /, \) and ensure proper sanitization before using parameters in file operations. Restrict file access permissions to prevent unauthorized file downloads.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35962 — 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-35962 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