CVE-2017-9765: Integer Overflow
A buffer overflow can cause an open unsecured server to crash after 2GB (greater than 2147483711 bytes to trigger the software bug)) XML message is received. Fortunately, the overflowing data after 2GB is cleaned up in the buffer which means that the chances of exploiting this flaw (by injecting code) is significantly reduced in gSOAP versions affected.
References:
https://www.genivia.com/advisory.html
Other sources
Integer overflow in the soapget function in Genivia gSOAP 2.7.x and 2.8.x before 2.8.48, as used on Axis cameras and other devices, allows remote attackers to execute arbitrary code or cause a denial of service (stack-based buffer overflow and application crash) via a large XML document, aka Devil's Ivy. NOTE: the large document would be blocked by many common web-server configurations on general-purpose computers.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2017-9765?
CVE-2017-9765 is classified as a moderate severity vulnerability due to the potential for a buffer overflow that could lead to a crash of the affected server.
How do I fix CVE-2017-9765?
To mitigate CVE-2017-9765, upgrade to gSOAP version 2.8.48 or later.
Which software versions are affected by CVE-2017-9765?
CVE-2017-9765 affects gSOAP versions 2.7.0 through 2.8.47.
Can CVE-2017-9765 be exploited remotely?
While CVE-2017-9765 shows a potential for exploitation, the buffer overflow is unlikely to be exploitable due to data cleanup after exceeding 2GB.
What type of vulnerability is CVE-2017-9765?
CVE-2017-9765 is a buffer overflow vulnerability caused by the handling of large XML messages in gSOAP.