Home/CVE/Anviz Global M3 Outdoor RFID Access Control executes any command received from any source. No authentication/encryption
CVE
CVE-2019-11523
Anviz Global M3 Outdoor RFID Access Control executes any command received from any source. No authentication/encryption
Anviz Global M3 Outdoor RFID Access Control executes any command received from any source. No authentication/encryption is done. Attackers can fully interact with the device: for example, send the "open door" command, download the users list (which includes RFID codes and passcodes in cleartext), or update/create users.
The same attack can be executed on a local network and over the internet (if the device is exposed on a public IP address).
CRITICAL · CVSS 9.8
EPSS 0.02511
Act now
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2019-11523, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
6Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1005 · Data from Local System T1040 · Network Sniffing T1056.004 · Credential API Hooking T1111 · Multi-Factor Authentication Interception T1539 · Steal Web Session Cookie T1552.004 · Private Keys
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-12 · Choosing Message Identifier CAPEC-CAPEC-157 · Sniffing Attacks CAPEC-CAPEC-158 · Sniffing Network Traffic CAPEC-CAPEC-166 · Force the System to Reset Values CAPEC-CAPEC-204 · Lifting Sensitive Data Embedded in Cache CAPEC-CAPEC-216 · Communication Channel Manipulation CAPEC-CAPEC-31 · Accessing/Intercepting/Modifying HTTP Cookies CAPEC-CAPEC-36 · Using Unpublished Interfaces or Functionality CAPEC-CAPEC-37 · Retrieve Embedded Sensitive Data CAPEC-CAPEC-383 · Harvesting Information via API Event Monitoring CAPEC-CAPEC-384 · Application API Message Manipulation via Man-in-the-Middle CAPEC-CAPEC-385 · Transaction or Event Tampering via Application API Manipulation
⬡
Weakness Classification
▤
Affected Products & Versions
1anviz m3 firmwareall versions
⚠
Public Exploits & PoCs
5These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
▣
Scoring & Timeline
9.8
CRITICAL · CVSS v3.0 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High