CVE-2019-3907: Premisys Identicard version 3.1.190 stores user credentials and other sensitive information with a known weak

This month

HIGH 7.5REMOTEDOWNGRADE

CVE-2019-3907 is a high-severity flaw (CVSS 7.5) affecting premisys id. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Premisys Identicard version 3.1.190 stores user credentials and other sensitive information with a known weak encryption method (MD5 hash of a salt and password).

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-798, CWE-916
Published	2019-01-18
Last modified	2026-06-17

Publisher (CNA): Tenable Network Security, Inc. · Vendor: identicard

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-01-18 18:29 UTCPublished CVE record published
2026-06-17 02:35 UTCUpdated Record last modified

identicard premisys id DOWNGRADE

Affected: 3.1.190

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.1.190

1. Check installed version

apt-cache policy premisys-id || rpm -q premisys-id || premisys-id --version

2. No fixed release: DOWNGRADE to a release before 3.1.190 (Debian / Ubuntu)

apt-cache madison premisys-id sudo apt install premisys-id=<VERSION_BEFORE_3.1.190> sudo apt-mark hold premisys-id

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list premisys-id sudo dnf downgrade premisys-id-<VERSION_BEFORE_3.1.190> sudo dnf versionlock add premisys-id

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-3907?

premisys id: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-3907 being exploited?

CVE-2019-3907 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-3907 affect?

CVE-2019-3907 affects premisys id. Severity is high (CVSS 7.5). Premisys Identicard version 3.1.190 stores user credentials and other sensitive information with a known weak encryption method (MD5 hash of a salt and password).

How urgent is CVE-2019-3907?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-3909 CRITICAL 9.8 DOWNGRADE Premisys Identicard version 3.1.190 database uses default credentials
CVE-2019-3908 HIGH 7.5 DOWNGRADE Premisys Identicard version 3.1.190 stores backup files as encrypted zip files
CVE-2019-3906 HIGH 8.8 DOWNGRADE Premisys Identicard version 3.1.190 contains hardcoded credentials in the WCF service on port 9003

References

← Back to latest CVEs