# CVE-2017-10720: Memory corruption in n/a > A stack overflow in the Shekar Endoscope desktop application allows remote code execution via a long Wi-Fi name, compromising user data. - **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 17 Jun 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-649q-q4wv-3x3j ## What is CVE-2017-10720? CVE-2017-10720 is a high-severity memory corruption vulnerability in n/a, published on 17 Jun 2019. It can only be exploited from the same machine or local 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 the desktop application used to connect to the device suffers from a stack overflow if more than 26 characters are passed to it as the Wi-Fi name. This application is installed on the device and an attacker who can provide the right payload can execute code on the user's system directly. Any breach of this system can allow an attacker to get access to all the data that the user has access too. The application uses a dynamic link library(DLL) called "avilib.dll" which is used by the application to send binary packets to the device that allow to control the device. One such action that the DLL provides is change password in the function "sendchangename" which allows a user to change the Wi-Fi name on the device. This function calls a sub function "sub_75876EA0" at address 0x758784F8. The function determines which action to execute based on the parameters sent to it. The "sendchangename" passes the datastring as the second argument which is the name we enter in the textbox and integer 1 as first argument. The rest of the 3 arguments are set to 0. The function "sub_75876EA0" at address 0x75876F19 uses the first argument received and to determine which block to jump to. Since the argument passed is 1, it jumps to 0x75876F20 and proceeds from there to address 0x75876F56 which calculates the length of the data string passed as the first parameter. This length and the first argument are then passed to the address 0x75877001 which calls the memmove function which uses a stack address as the destination where the password typed by us is passed as the source and length calculated above is passed as the number of bytes to copy which leads to a stack overflow. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2017-10720? It affects 1 product. Products: Ishekar Endoscope Camera Firmware. ## How do I fix CVE-2017-10720? No fix has been published for CVE-2017-10720 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-10720 being exploited? There is no known exploitation of CVE-2017-10720 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-10723](https://insights.sbomify.com/CVE-2017-10723/): Memory corruption in n/a (high 8.8) - [CVE-2017-10724](https://insights.sbomify.com/CVE-2017-10724/): Memory corruption in n/a (high 8.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-10720 and fix it if it is affected. What it is: CVE-2017-10720 is a high-severity memory corruption vulnerability in n/a, published on 17 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-10720 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-10720/ (Markdown: https://insights.sbomify.com/CVE-2017-10720/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-10720 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10720 - OSV: https://osv.dev/vulnerability/CVE-2017-10720 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-10720/ Summaries are generated and may contain mistakes; the official description above is the record.