# CVE-2020-11681: Information disclosure in n/a

> Low-privileged users can view cleartext SMTP credentials and create admin accounts in Castel NextGen DVR systems.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p6qr-x996-pvwx

## What is CVE-2020-11681?

CVE-2020-11681 is a high-severity vulnerability in n/a, published on 4 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Castel NextGen DVR v1.0.0 stores and displays credentials for the associated SMTP server in cleartext. Low privileged users can exploit this to create an administrator user and obtain the SMTP credentials.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Castel Nextgen Dvr Firmware.

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

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

## Is CVE-2020-11681 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11679](https://insights.sbomify.com/CVE-2020-11679/): Missing authorization in n/a (high 8.8)
- [CVE-2020-11680](https://insights.sbomify.com/CVE-2020-11680/): Missing authorization in n/a (medium 6.5)
- [CVE-2020-11682](https://insights.sbomify.com/CVE-2020-11682/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11681 is a high-severity vulnerability in n/a, published on 4 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11681 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-11681/ (Markdown: https://insights.sbomify.com/CVE-2020-11681/index.md)
```

## Sources

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

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