# CVE-2020-11719: Weak cryptography in n/a

> Programi Bilanc uses a weak static encryption key, allowing attackers to decrypt data and bypass security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 23 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6j7q-rmrp-5g6f

## What is CVE-2020-11719?

CVE-2020-11719 is a high-severity vulnerability in n/a, published on 23 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and possibly below. It relies on broken encryption with a weak and guessable static encryption key.

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

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

It affects 1 product.


Products: Bilanc Bilanc.

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

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

## Is CVE-2020-11719 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11720](https://insights.sbomify.com/CVE-2020-11720/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-11717](https://insights.sbomify.com/CVE-2020-11717/): SQL injection in n/a (critical 9.8)
- [CVE-2020-8995](https://insights.sbomify.com/CVE-2020-8995/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-11718](https://insights.sbomify.com/CVE-2020-11718/): Other in n/a (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11719 is a high-severity vulnerability in n/a, published on 23 Dec 2020. 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-2020-11719 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-11719/ (Markdown: https://insights.sbomify.com/CVE-2020-11719/index.md)
```

## Sources

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

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