# CVE-2020-24056: Hardcoded credentials in n/a

> Hardcoded credentials in Verint cameras allow attackers to access FTP, Telnet, or SSH services, compromising confidentiality.

- **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:** 21 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4xwv-xw85-x4w9

## What is CVE-2020-24056?

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

### Official description

A hardcoded credentials vulnerability exists in Verint 5620PTZ Verint_FW_0_42, Verint 4320 V4320_FW_0_23, V4320_FW_0_31, and Verint S5120FD Verint_FW_0_42units. This could cause a confidentiality issue when using the FTP, Telnet, or SSH protocols.

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

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

It affects 3 products.


Products: Verint 4320 Firmware, Verint 5620ptz Firmware, Verint S5120fd Firmware.

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

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

## Is CVE-2020-24056 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24055](https://insights.sbomify.com/CVE-2020-24055/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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