CVE-2019-3908
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 · uneditedPremisys Identicard version 3.1.190 stores backup files as encrypted zip files. The password to the zip is hard-coded and unchangeable. An attacker with access to these backups can decrypt them and obtain sensitive data.
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 confidencePremisys Identicard v3.1.190 stores backup files as password-protected ZIP archives, but the encryption password is hard-coded into the application and cannot be changed by administrators. Anyone who obtains these backup files can decrypt them using the known hard-coded password, exposing sensitive system data.
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.1.190CVSS 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.
-
Check if Identicard Premisys Id v3.1.190 is installedLocate the Premisys Identicard installation on the system. Check the application version by opening the software, navigating to Help > About, or inspecting the executable file properties. Compare your installed version to 3.1.190.Affected if The installed version is Identicard Premisys Id version 3.1.190 exactly.
-
Locate backup files created by Identicard Premisys IdSearch for backup files on the system. Typical locations include the application data folder, designated backup directories, or custom paths configured during installation. Look for files with .zip or .bak extensions that correspond to Identicard backup operations.Affected if Backup files created by Identicard Premisys Id exist on the system.
-
Verify backup files are password-protected ZIP archivesInspect the backup files using a ZIP utility (such as 7-Zip or the operating system's built-in archive handler). Attempt to open or list the contents of the backup file - it should prompt for a password, confirming it is encrypted.Affected if The backup files are password-protected ZIP archives requiring a password to extract contents.
-
Check access controls on backup filesReview file system permissions on the Identicard backup files. Use operating system tools (such as icacls on Windows or ls -la on Linux/Unix) to list which users and groups have read access to the backup files.Affected if Backup files are accessible to users beyond trusted administrators, allowing unauthorized extraction of the archive contents.
You are affected if Identicard Premisys Id version 3.1.190 is installed and password-protected backup files exist with accessible permissions, since the hard-coded encryption password allows anyone to decrypt those backups.
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 dataUntil the vendor releases a patch allowing configurable or user-managed encryption passwords, organizations should restrict access to backup files to trusted personnel only, store backups in secure locations with access controls, and consider implementing additional encryption layers around the backup storage.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3908 — 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-3908 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