Security readout for executives and security teams
Plain-English summary
FaceSentry access control systems store passwords in cleartext in a local SQLite database. If an attacker can access that database, they can read credentials without cracking them. This matters because FaceSentry is tied to physical access control, so exposed credentials may affect both cyber and facility security.
Executive priority
Treat as high priority where FaceSentry controls sensitive facilities or is reachable from broad networks. Prioritize inventory, access restriction, vendor remediation review, and credential rotation planning.
Technical view
CVE-2019-25279 is CWE-312 cleartext storage of sensitive information in iWT Ltd. FaceSentry Access Control System. Reported affected builds include 6.4.8 build 264, 5.7.2 build 568, and 5.7.0 build 539. The CVSS 3.1 score is 7.5, with high confidentiality impact and no privileges or user interaction required.
Likely exposure
Exposure is likely limited to organizations running the affected FaceSentry builds. Risk increases if the appliance or its web components are reachable from untrusted networks, or if attackers can access the device filesystem or database.
Exploitation context
The source bundle includes a Packet Storm exploit entry, indicating public exploit-related material exists. CISA KEV status is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Evidence supports cleartext credential storage and affected build details, but the provided sources do not name a vendor patch, workaround, or confirmed active exploitation. Avoid assuming broader product versions beyond those listed.
Mitigation direction
- Identify all FaceSentry systems and confirm exact version and build.
- Check iWT Ltd. or integrator guidance for fixed firmware or supported remediation.
- Restrict network access to FaceSentry management interfaces.
- Limit filesystem and database access on the appliance.
- Rotate FaceSentry credentials after remediation or containment.
- Monitor for unexpected access to FaceSentry database files.
Validation and detection
- Inventory FaceSentry appliances and record version/build information.
- Confirm whether affected builds are present: 6.4.8, 5.7.2, or 5.7.0 listed builds.
- Review whether passwords are stored unencrypted in the FaceSentry SQLite database.
- Check access logs for unauthorized management, filesystem, or database access.
- Verify vendor or integrator remediation has been applied where available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-312: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25279 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- Zero Science Lab Vulnerability AdvisoryCVE reference · third-party-advisory
- IBM X-Force Exchange Vulnerability EntryCVE reference · vdb-entry
- Packet Storm Security Exploit EntryCVE reference · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cleartext Storage of Sensitive Information
Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.