CVE-2019-3906
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 contains hardcoded credentials in the WCF service on port 9003. An authenticated remote attacker can use these credentials to access the badge system database and modify its contents.
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 version 3.1.190 contains hardcoded credentials embedded in the WCF service listening on port 9003. An authenticated remote attacker with knowledge of these credentials can gain unauthorized access to the badge system database and modify its contents.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Identicard Premisys versionCheck the installed version of Identicard Premisys Id software on the system. Look in the application properties, installed programs list, or software registry for the exact version number.Affected if The installed version is exactly 3.1.190
-
Confirm WCF service is running on port 9003Use netstat or a port scanner to determine if the system is listening on TCP port 9003, which is the port the vulnerable WCF service uses.Affected if Port 9003 is open and accepting connections
-
Check if the WCF service is network accessibleDetermine whether port 9003 is exposed to the network or only bound to localhost. Attempt to connect to the WCF service endpoint from a remote system or verify firewall rules.Affected if The WCF service on port 9003 is accessible from network segments outside the local host
-
Inspect application for hardcoded credentialsExamine the Identicard application directory, particularly WCF service configuration files and binaries, for embedded credentials, default accounts, or hardcoded password strings.Affected if Hardcoded credentials or default accounts are found in the application files or configuration
A user is affected if they are running Identicard Premisys Id version 3.1.190 with the WCF service on port 9003 exposed and accessible, and the hardcoded credentials are present in the deployment.
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 dataReplace hardcoded credentials with secure authentication mechanisms (e.g., integrated Windows authentication, certificate-based auth, or external identity provider), remove default accounts, restrict network access to port 9003, and audit for additional hardcoded secrets.
- Consultation6.0 h
- Implementation12.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3906 — 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-3906 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