CVE-2007-3917: High severity Wesnoth Wesnoth vulnerability
Description of problem:
From Novell bugzilla (see URL):
A malicious user could send a long chat message with multibyte characters, the server would truncate the message on a fixed length, without paying attention to the multibyte characters. This led to invalid utf-8 on the client and an uncaught exception was thrown. Note both wesnoth and the wesnoth server are affected.
Additional information:
I am aware of no further details, nor the fix.
Other sources
The multiplayer engine in Wesnoth 1.2.x before 1.2.7 and 1.3.x before 1.3.9 allows remote servers to cause a denial of service (crash) via a long message with multibyte characters that can produce an invalid UTF-8 string after it is truncated, which triggers an uncaught exception, involving the truncatemessage function in server/server.cpp. NOTE: this issue affects both clients and servers.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2007-3917?
CVE-2007-3917 is classified as a moderate severity vulnerability.
How do I fix CVE-2007-3917?
To mitigate CVE-2007-3917, update to the latest version of the Wesnoth package that includes the fix.
What impact does CVE-2007-3917 have on affected systems?
CVE-2007-3917 can lead to invalid UTF-8 character handling on the client, potentially causing application crashes or unexpected behavior.
Which software versions are affected by CVE-2007-3917?
CVE-2007-3917 affects Wesnoth versions 1.2.0 through 1.3.8.
Is CVE-2007-3917 exploitable remotely?
Yes, CVE-2007-3917 can be exploited remotely by sending a specially crafted long chat message.