{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-42363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42363 is a critical vulnerability in GeoVision Inc. GV-IP Device Utility, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-42363 and fix it if it is affected.\n\nWhat it is: CVE-2026-42363 is a critical vulnerability in GeoVision Inc. GV-IP Device Utility, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-42363 in the wild and no public exploit code.\n\nAffected product: GeoVision Inc. GV-IP Device Utility. 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-2026-42363/ (Markdown: https://insights.sbomify.com/CVE-2026-42363/index.md)","id":"CVE-2026-42363","markdown":"https://insights.sbomify.com/CVE-2026-42363/index.md","name":"CVE-2026-42363","record":{"aliases":["GHSA-wcj5-244x-rmgx"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"GeoVision device utility","requires_auth":"none","summary":"An attacker on the same LAN can decrypt broadcasted credentials due to weak encryption, gaining full control over GeoVision device configurations.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GV","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-656","name":"Reliance on Security Through Obscurity"}],"description":"An insufficient encryption vulnerability exists in the Device Authentication functionality of GeoVision GV-IP Device Utility 9.0.5. Listening to broadcast packets can lead to credentials leak. An attacker can listen to broadcast messages to trigger this vulnerability.\n\nWhen interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the \"obscurity\" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default.","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":"GeoVision GV-IP Device Utility Device Authentication insufficient encryption vulnerability","id":"CVE-2026-42363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"GeoVision LPC2011/LPC2211 Web Interface / DdnsSetting.cgi OS command injection vulnerability","id":"CVE-2026-42364"},"packages":[],"prev":{"headline":"Apache Airflow: Rendered template truncation bypasses nested sensitive-key masking","id":"CVE-2026-42360"},"products":["GV-IP Device Utility"],"published":"2026-04-26","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-27","vendors":["GeoVision Inc."]},"summary":"An attacker on the same LAN can decrypt broadcasted credentials due to weak encryption, gaining full control over GeoVision device configurations.","url":"https://insights.sbomify.com/CVE-2026-42363/"}