# CVE-2017-10723: Memory corruption in n/a > An attacker on the device Wi-Fi can trigger a buffer overflow in the UDP daemon to execute remote code and access video feeds. - **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **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:** 17 Jun 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-8mjp-v767-xr8v ## What is CVE-2017-10723? CVE-2017-10723 is a high-severity memory corruption vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Recently it was discovered as a part of the research on IoT devices in the most recent firmware for Shekar Endoscope that an attacker connected to the device Wi-Fi SSID can exploit a memory corruption issue and execute remote code on the device. This device acts as an Endoscope camera that allows its users to use it in various industrial systems and settings, car garages, and also in some cases in the medical clinics to get access to areas that are difficult for a human being to reach. Any breach of this system can allow an attacker to get access to video feed and pictures viewed by that user and might allow them to get a foot hold in air gapped networks especially in case of nation critical infrastructure/industries. The firmware contains binary uvc_stream that is the UDP daemon which is responsible for handling all the UDP requests that the device receives. The client application sends a UDP request to change the Wi-Fi name which contains the following format: "SETCMD0001+0001+[2 byte length of wifiname]+[Wifiname]. This request is handled by "control_Dev_thread" function which at address "0x00409AE0" compares the incoming request and determines if the 10th byte is 01 and if it is then it redirects to 0x0040A74C which calls the function "setwifiname". The function "setwifiname" uses a memcpy function but uses the length of the payload obtained by using strlen function as the third parameter which is the number of bytes to copy and this allows an attacker to overflow the function and control the $PC value. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2017-10723? It affects 1 product. Products: Ishekar Endoscope Camera Firmware. ## How do I fix CVE-2017-10723? No fix has been published for CVE-2017-10723 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-10723 being exploited? There is no known exploitation of CVE-2017-10723 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-10724](https://insights.sbomify.com/CVE-2017-10724/): Memory corruption in n/a (high 8.8) - [CVE-2017-10720](https://insights.sbomify.com/CVE-2017-10720/): Memory corruption in n/a (high 7.8) - [CVE-2017-10722](https://insights.sbomify.com/CVE-2017-10722/): Memory corruption in n/a (high 7.8) - [CVE-2017-10718](https://insights.sbomify.com/CVE-2017-10718/): Missing authorization in n/a (medium 6.5) - [CVE-2017-10719](https://insights.sbomify.com/CVE-2017-10719/): Hardcoded credentials in n/a (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-10723 and fix it if it is affected. What it is: CVE-2017-10723 is a high-severity memory corruption vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-10723 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-2017-10723/ (Markdown: https://insights.sbomify.com/CVE-2017-10723/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-10723 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10723 - OSV: https://osv.dev/vulnerability/CVE-2017-10723 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-10723/ Summaries are generated and may contain mistakes; the official description above is the record.