CVE-2019-3908

HIGHNVD 7.57.5—Trending — 3 sources updated this week

7.5

Premisys 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.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 70.9%
KEV: Not listed

Published

January 18, 2019

Last Modified

November 21, 2024

References (4)

vulnreport@tenablehttp://www.securityfocus.com/bid/106552
vulnreport@tenablehttps://www.tenable.com/security/research/tra-2019-01
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/106552
af854a3a-2127-422b-91ae-364da2661108https://www.tenable.com/security/research/tra-2019-01

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 23:07 UTCEG score recompute
2026-05-27 23:07 UTCGHSA enrichment
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:47 UTCepss_batch

Frequently asked(5)

What is CVE-2019-3908?

CVE-2019-3908 is a high vulnerability published on January 18, 2019. Premisys 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.

When was CVE-2019-3908 disclosed?

CVE-2019-3908 was first published in the National Vulnerability Database on January 18, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-3908 actively exploited?

CVE-2019-3908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-3908?

CVE-2019-3908 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2019-3908?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-3908, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-3908

Explore →

Is Your Infrastructure Affected by CVE-2019-3908?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-3908

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-3908?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)