OpenSLP CVE-2017-17833 Heap Memory Corruption Vulnerability
BID:104577
Info
OpenSLP CVE-2017-17833 Heap Memory Corruption Vulnerability
| Bugtraq ID: | 104577 |
| Class: | Failure to Handle Exceptional Conditions |
| CVE: |
CVE-2017-17833 |
| Remote: | Yes |
| Local: | No |
| Published: | Apr 23 2018 12:00AM |
| Updated: | Apr 23 2018 12:00AM |
| Credit: | Unknown |
| Vulnerable: |
Redhat Enterprise Linux 7 OpenSLP OpenSLP 1.0.2 0 OpenSLP OpenSLP 1.1 Lenovo ThinkServer TS460 0 Lenovo ThinkServer SR630 0 Lenovo ThinkServer RS160 0 Lenovo ThinkServer RQ750 0 Lenovo ThinkServer RD640 0 Lenovo ThinkServer RD540 0 Lenovo ThinkServer RD450X 0 Lenovo ThinkServer RD440 0 Lenovo ThinkServer RD350X 0 Lenovo ThinkServer RD340 0 Lenovo ThinkServer HR650X 0 Lenovo ThinkServer HR630X 0 Lenovo ThinkServer RD650 Lenovo ThinkServer RD550 Lenovo ThinkServer RD450 Lenovo ThinkServer RD350 Debian Linux 7.0 |
| Not Vulnerable: |
Lenovo ThinkServer TS460 2.32 Lenovo ThinkServer RS160 2.32 Lenovo ThinkServer RQ750 1.40 Lenovo ThinkServer RD650 4.53.351 Lenovo ThinkServer RD640 50.00 Lenovo ThinkServer RD550 4.53.351 Lenovo ThinkServer RD540 50.00 Lenovo ThinkServer RD450 4.53.351 Lenovo ThinkServer RD440 50.00 Lenovo ThinkServer RD350 4.53.351 Lenovo ThinkServer RD340 50.00 |
Discussion
OpenSLP CVE-2017-17833 Heap Memory Corruption Vulnerability
OpenSLP is prone to a heap-memory-corruption vulnerability.
An attacker can exploit this issue to crash the affected application or execute arbitrary code within the context of the affected application.
OpenSLP 1.0.2 and 1.1.0 are vulnerable.
OpenSLP is prone to a heap-memory-corruption vulnerability.
An attacker can exploit this issue to crash the affected application or execute arbitrary code within the context of the affected application.
OpenSLP 1.0.2 and 1.1.0 are vulnerable.
Exploit / POC
OpenSLP CVE-2017-17833 Heap Memory Corruption Vulnerability
Currently, we are not aware of any working exploits. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Currently, we are not aware of any working exploits. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].