{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2019-20461 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20461 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20461 is a critical vulnerability in n/a, published on 7 Nov 2024."},"fix_prompt":"Check this codebase for CVE-2019-20461 and fix it if it is affected.\n\nWhat it is: CVE-2019-20461 is a critical vulnerability in n/a, published on 7 Nov 2024. \nExploitation: There is no known exploitation of CVE-2019-20461 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-20461/ (Markdown: https://insights.sbomify.com/CVE-2019-20461/index.md)","id":"CVE-2019-20461","markdown":"https://insights.sbomify.com/CVE-2019-20461/index.md","name":"CVE-2019-20461","record":{"aliases":["GHSA-3mh2-26wx-247f"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"An issue was discovered on Alecto IVM-100 2019-11-12 devices.","id":"CVE-2019-20461","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-20462"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-20460"},"products":["n/a"],"published":"2024-11-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2019-20461/"}