LiveActive security incident?Get immediate response
CVE Record

CVE-2016-20030: ZKTeco ZKBioSecurity 3.0 User Enumeration via authLoginAction

ZKTeco ZKBioSecurity 3.0 contains a user enumeration vulnerability that allows unauthenticated attackers to discover valid usernames by submitting partial characters via the username parameter. Attackers can send requests to the authLoginAction!login.do script with varying username inputs to enumerate valid user accounts based on application responses.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability lets an unauthenticated internet user identify valid usernames in ZKTeco ZKBioSecurity 3.0 by observing login responses. On its own, user enumeration is usually a precursor issue, but it can materially improve password attacks and targeted intrusion attempts against physical access or biometric security management systems.

Executive priority

Prioritize if ZKBioSecurity is exposed outside trusted networks or manages sensitive access-control environments. Treat as a credential-attack enabler rather than proven system compromise. Reduce exposure quickly and seek vendor remediation guidance.

Technical view

CVE-2016-20030 affects ZKTeco ZKBioSecurity 3.0.1.0_R_230. The authLoginAction!login.do endpoint reportedly discloses whether submitted partial username values match valid accounts. The CVE record rates it CVSS 9.8, though the described primitive is username enumeration. Public references include an exploit-tagged Packet Storm entry.

Likely exposure

Exposure is most relevant where ZKBioSecurity 3.0.1.0_R_230 login interfaces are reachable by untrusted networks or the internet. Organizations using ZKTeco access-control or biometric management deployments should verify product version and interface exposure.

Exploitation context

Sources describe unauthenticated remote enumeration via login behavior. A public exploit reference exists, but the provided sources do not establish current active exploitation, and the CVE is not marked KEV in the supplied bundle.

Researcher notes

The public description centers on CWE-551 and username disclosure through response differences. The 9.8 CVSS score appears severe relative to the described behavior, so validate real-world impact in context. Avoid assuming code execution or data theft without additional evidence.

Mitigation direction

  • Identify any ZKBioSecurity 3.0.1.0_R_230 deployments.
  • Restrict access to the login interface from untrusted networks.
  • Check ZKTeco guidance for fixed versions or vendor-recommended mitigations.
  • Monitor authentication logs for unusual username probing patterns.
  • Apply compensating controls such as VPN or allowlisting where upgrade status is unclear.

Validation and detection

  • Confirm installed ZKBioSecurity version and build number.
  • Review whether authLoginAction!login.do is externally reachable.
  • Check web logs for repeated partial username login attempts.
  • Verify whether login responses differ for valid versus invalid usernames.
  • Document remediation status against vendor or third-party advisory guidance.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-551: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-20030 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2016-20030Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZKTeco Inc.ZKTeco ZKBioSecurity3.0.1.0_R_230Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-551 · source CWE mapping

Incorrect Behavior Order: Authorization Before Parsing and Canonicalization

Incorrect Behavior Order: Authorization Before Parsing and Canonicalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.