CVE-2019-12388
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 · uneditedAnviz access control devices perform cleartext transmission of sensitive information (passwords/pins and names) when replying to query on port tcp/5010.
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 confidenceAnviz access control devices transmit sensitive authentication credentials (passwords/PINs) and user names in cleartext over TCP port 5010 when responding to queries, allowing network eavesdroppers to intercept these 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 dataall versionsCVSS 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 Anviz access control deviceCheck the device model/manufacturer through device documentation, management interface, or physical labeling. Look for 'Anviz' branding or model numbers associated with Anviz access control products.Affected if The device is an Anviz access control device (any model)
-
Verify TCP port 5010 is listeningPerform a port scan against the device IP address targeting TCP port 5010 using tools such as 'nmap -p 5010 <device_ip>' or 'netstat' on the device if accessible.Affected if TCP port 5010 is open and responding on the device
-
Confirm cleartext protocol on port 5010Capture network traffic from the device on port 5010 using a packet sniffer (such as Wireshark or tcpdump) while the device responds to queries. Inspect the captured packets for plaintext transmission of usernames and passwords/PINs.Affected if Authentication credentials (usernames, passwords, or PINs) are transmitted in cleartext within the captured traffic on port 5010
-
Assess network exposure of port 5010Determine if port 5010 is accessible from network segments that contain untrusted users or systems. Check firewall rules, ACLs, or VLAN configuration to identify if the management port is exposed beyond isolated management networks.Affected if Port 5010 is accessible from network segments outside of a trusted management network
If the device is an Anviz access control unit with TCP port 5010 exposed and communicating authentication credentials in cleartext, the environment is affected by this CVE.
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 network segmentation to isolate access control devices and/or deploy VPN tunneling for device management traffic; verify vendor firmware updates for encrypted communication support.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12388 — 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-2019-12388 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