# CVE-2019-20461: An issue was discovered on Alecto IVM-100 2019-11-12 devices.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-3mh2-26wx-247f

## What is CVE-2019-20461?

CVE-2019-20461 is a critical vulnerability in n/a, published on 7 Nov 2024. 

### Official description

An issue was discovered on Alecto IVM-100 2019-11-12 devices. The device uses a custom UDP protocol to start and control video and audio services. The protocol has been partially reverse engineered. Based upon the reverse engineering, no password or username is ever transferred over this protocol. Thus, one can set up the camera connection feed with only the encoded UID. It is possible to set up sessions with the camera over the Internet by using the encoded UID and the custom UDP protocol, because authentication happens at the client side.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2019-20461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20461 is a critical vulnerability in n/a, published on 7 Nov 2024. 
Exploitation: There is no known exploitation of CVE-2019-20461 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-20461/ (Markdown: https://insights.sbomify.com/CVE-2019-20461/index.md)
```

## Sources

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

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