CVE-2019-5723 json
An issue was discovered in portier vision 4.4.4.2 and 4.4.4.6.
published 7y ago modified 4mo ago also EUVD-2019-15297
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2019-5723 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/151118/PORTIER-4.4.4.2-4.4.4.6-Cryptographic-Issues.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org https://seclists.org/bugtraq/2019/Jan/8 referenced PoC, tagged "exploit" by a source, unverified
- syss.de https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2018-011.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
References
-
packetstormsecurity.com
/files/151118/PORTIER-4.4.4.2-4.4.4.6-Cryptographic-Issues.html
exploit, third-party-advisory, vdb-entry
-
seclists.org
/bugtraq/2019/Jan/8
mailing-list, exploit, third-party-advisory
-
syss.de
/fileadmin/dokumente/Publikationen/Advisories/SYSS-2018-011.txt
exploit, third-party-advisory
Sources
- CVE List CVE-2019-5723
- NVD CVE-2019-5723
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.