CVE-2023-38958
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 · uneditedAn access control issue in ZKTeco BioAccess IVS v3.3.1 allows unauthenticated attackers to arbitrarily close and open the doors managed by the platform remotely via sending a crafted web request.
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 BioAccess IVS v3.3.1 contains an authentication bypass vulnerability allowing unauthenticated remote attackers to open and close managed doors by sending crafted HTTP requests. The access control failure enables complete unauthorized control of physical access points without any credentials.
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.1CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 the BioAccess IVS installation versionLocate the installed version through the product's web interface (typically in System > About or System > License), administrative console, or by checking the software inventory/registry entries where the application stores its version informationAffected if The installed version is exactly 3.3.1, matching the vulnerable release
-
Confirm the HTTP management interface is accessibleAttempt to access the BioAccess IVS web portal via browser or HTTP client on the configured port (commonly 8080 or 8443 for this product line)Affected if The web interface is reachable and responds, indicating the attack surface is active
-
Verify door control endpoint exposureSend a crafted HTTP request to typical door control endpoints (such as /door/open, /door/close, or API paths controlling relay outputs) without providing any authentication credentialsAffected if The door control endpoints respond with success or execute the requested action without requiring authentication, confirming the bypass exists
-
Assess network accessibility of the management interfaceDetermine if the BioAccess IVS HTTP service is bound to any IP address other than localhost, or is reachable from network segments beyond the trusted internal networkAffected if The interface is exposed to untrusted networks or the internet, increasing exploitation likelihood
A user is affected if BioAccess IVS version 3.3.1 is installed AND the HTTP door control endpoints accept and execute commands without any authentication 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.
From vendor dataApply vendor security patches immediately if available; until patched, restrict network exposure using firewalls/VPNs and implement WAF rules to detect and block anomalous door control requests.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38958 — 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-38958 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