Skip to content
Fencer Intel
medium 5.5

CVE-2020-6857 json

CarbonFTP v1.4 uses insecure proprietary password encryption with a hard-coded weak encryption key.

published 6y ago modified 4mo ago also EUVD-2020-28000

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits
1
Exploit-DB

Summary

CarbonFTP v1.4 uses insecure proprietary password encryption with a hard-coded weak encryption key. The key for local FTP server passwords is hard-coded in the binary.

Is CVE-2020-6857 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 Fencer

Timeline

  1. Published
  2. First public exploit (EDB-48363)

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-48363 Neowise CarbonFTP 1.4 - Insecure Proprietary Password Encryption remote, 2020-04-21
  • hyp3rlinx.altervista.org http://hyp3rlinx.altervista.org referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org https://seclists.org/bugtraq/2020/Jan/30 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/156015/Neowise-CarbonFTP-1.4-Insecure-Proprietary-Password-Encryption.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2020/Jan/29 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2020/Jan/35 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/157321/Neowise-CarbonFTP-1.4-Insecure-Proprietary-Password-Encryption.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm
  • CWE-798 Use of Hard-coded Credentials

References

Sources

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.