# CVE-2020-10292: Service DoS through arbitrary pointer dereferencing on KUKA simulator > An unauthenticated attacker can cause a denial of service in the KUKA Visual Components network license server via arbitrary pointer dereferencing. - **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 6 Nov 2020 - **Updated:** 17 Sep 2024 - **Also known as:** GHSA-vcjx-vhg2-3wr3 ## What is CVE-2020-10292? CVE-2020-10292 is a high-severity vulnerability in KUKA Roboter GmbH Visual Components Network License Server 2.0.8, published on 6 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Visual Components (owned by KUKA) is a robotic simulator that allows simulating factories and robots in order toimprove planning and decision-making processes. Visual Components software requires a special license which can beobtained from a network license server. The network license server binds to all interfaces (0.0.0.0) and listensfor packets over UDP port 5093. No authentication/authorization is required in order to communicate with theserver. The protocol being used is a property protocol by RMS Sentinel which provides the licensing infrastructurefor the network license server. RMS Sentinel license manager service exposes UDP port 5093 which provides sensitivesystem information that could be leveraged for further exploitation without any kind of authentication. Thisinformation includes detailed hardware and OS characteristics.After a decryption process, a textual protocol is found which contains a simple header with the requested command,application-identifier, and some arguments. The protocol is vulnerable to DoS through an arbitrary pointerderreference. This flaw allows an attacker to to pass a specially crafted package that, when processed by theservice, causes an arbitrary pointer from the stack to be dereferenced, causing an uncaught exception thatterminates the service. This can be further contructed in combination with RVDP#710 which exploits an informationdisclosure leak, or with RVDP#711 for an stack-overflow and potential code execution.Beyond denying simulations, Visual Components provides capabilities to interface with industrial machinery andautomate certain processes (e.g. testing, benchmarking, etc.) which depending on the DevOps setup might beintegrated into the industrial flow. Accordingly, a DoS in the simulation might have higher repercusions, dependingon the Industrial Control System (ICS) ICS infrastructure. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-248 (Uncaught Exception) ## Which versions are affected by CVE-2020-10292? It affects 1 product. Products: Kuka Visual Components Network License Server. ## How do I fix CVE-2020-10292? No fix has been published for CVE-2020-10292 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-10292 being exploited? There is no known exploitation of CVE-2020-10292 in the wild and no public exploit code. ## Other vulnerabilities in KUKA Roboter GmbH Visual Components Network License Server 2.0.8 - [CVE-2020-10291](https://insights.sbomify.com/CVE-2020-10291/): RVD#3336: System information disclosure without authentication on KUKA simulators (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-10292 and fix it if it is affected. What it is: CVE-2020-10292 is a high-severity vulnerability in KUKA Roboter GmbH Visual Components Network License Server 2.0.8, published on 6 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-10292 in the wild and no public exploit code. Affected product: KUKA Roboter GmbH Visual Components Network License Server 2.0.8. 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-2020-10292/ (Markdown: https://insights.sbomify.com/CVE-2020-10292/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10292 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10292 - OSV: https://osv.dev/vulnerability/CVE-2020-10292 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-10292/ Summaries are generated and may contain mistakes; the official description above is the record.