# CVE-2020-10552: Hardcoded credentials in n/a

> Attackers can access the Firebird database using default credentials to read and modify sensitive data, including passwords.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gmfw-w846-fjh2

## What is CVE-2020-10552?

CVE-2020-10552 is a high-severity vulnerability in n/a, published on 5 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Psyprax before 3.2.2. The Firebird database is accessible with the default user sysdba and password masterke after installation. This allows any user to access it and read and modify the contents, including passwords. Local database files can be accessed directly as well.

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

## Which versions are affected by CVE-2020-10552?

It affects 1 product.


Products: Psyprax Psyprax.

## How do I fix CVE-2020-10552?

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

## Is CVE-2020-10552 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10554](https://insights.sbomify.com/CVE-2020-10554/): Weak cryptography in n/a (high 7.5)
- [CVE-2020-10553](https://insights.sbomify.com/CVE-2020-10553/): Security feature bypass in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10552 and fix it if it is affected.

What it is: CVE-2020-10552 is a high-severity vulnerability in n/a, published on 5 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10552 in the wild and no public exploit code.

Affected product: n/a. 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-2020-10552/ (Markdown: https://insights.sbomify.com/CVE-2020-10552/index.md)
```

## Sources

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

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