# CVE-2019-3909: Hardcoded credentials in Premisys Identicard 3.1.190

> Premisys Identicard uses default database credentials that cannot be changed by users, allowing attackers to gain unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-999g-r275-5mjf

## What is CVE-2019-3909?

CVE-2019-3909 is a critical vulnerability in Premisys Identicard 3.1.190, published on 18 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Premisys Identicard version 3.1.190 database uses default credentials. Users are unable to change the credentials without vendor intervention.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2019-3909?

It affects 1 product.


Products: Identicard Premisys Id.

## How do I fix CVE-2019-3909?

No fix has been published for CVE-2019-3909 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3909 being exploited?

There is no known exploitation of CVE-2019-3909 in the wild and no public exploit code.

## Other vulnerabilities in Premisys Identicard 3.1.190

- [CVE-2019-3906](https://insights.sbomify.com/CVE-2019-3906/): Hardcoded credentials in Premisys Identicard 3.1.190 (high 8.8)
- [CVE-2019-3907](https://insights.sbomify.com/CVE-2019-3907/): Weak cryptography in Premisys Identicard 3.1.190 (high 7.5)
- [CVE-2019-3908](https://insights.sbomify.com/CVE-2019-3908/): Hardcoded credentials in Premisys Identicard 3.1.190 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3909 and fix it if it is affected.

What it is: CVE-2019-3909 is a critical vulnerability in Premisys Identicard 3.1.190, published on 18 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3909 in the wild and no public exploit code.

Affected product: Premisys Identicard 3.1.190. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-3909/ (Markdown: https://insights.sbomify.com/CVE-2019-3909/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3909
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3909
- OSV: https://osv.dev/vulnerability/CVE-2019-3909

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3909/
Summaries are generated and may contain mistakes; the official description above is the record.