# CVE-2022-25577: Hardcoded credentials in n/a

> Attackers with system access can read and modify user data due to a hardcoded password used to encrypt the SQLite database.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qvg3-jj6j-c973

## What is CVE-2022-25577?

CVE-2022-25577 is a critical vulnerability in n/a, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ALF-BanCO v8.2.5 and below was discovered to use a hardcoded password to encrypt the SQLite database containing the user's data. Attackers who are able to gain remote or local access to the system are able to read and modify the data.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-25577?

It affects 1 product.


Products: Alf-Banco Alf-Banco.

## How do I fix CVE-2022-25577?

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

## Is CVE-2022-25577 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25577 and fix it if it is affected.

What it is: CVE-2022-25577 is a critical vulnerability in n/a, published on 25 Mar 2022. 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-2022-25577 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-2022-25577/ (Markdown: https://insights.sbomify.com/CVE-2022-25577/index.md)
```

## Sources

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

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