# CVE-2019-5723: Weak cryptography in n/a

> Attackers can easily decrypt stored passwords due to weak, reversible encryption with a static key in Portier Vision.

- **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:** 19 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pgqj-8c52-846r

## What is CVE-2019-5723?

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

### Official description

An issue was discovered in portier vision 4.4.4.2 and 4.4.4.6. Passwords are stored using reversible encryption rather than as a hash value, and the used Vigenere algorithm is badly outdated. Moreover, the encryption key is static and too short. Due to this, the passwords stored by the application can be easily decrypted.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Portier Portier.

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

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

## Is CVE-2019-5723 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-5722](https://insights.sbomify.com/CVE-2019-5722/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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