First published: Tue Oct 09 2007(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/1.2.7 | <1. | 1. |
The Battle for Wesnoth | =1.2 | |
The Battle for Wesnoth | =1.2.1 | |
The Battle for Wesnoth | =1.2.2 | |
The Battle for Wesnoth | =1.2.3 | |
The Battle for Wesnoth | =1.2.4 | |
The Battle for Wesnoth | =1.2.5 | |
The Battle for Wesnoth | =1.2.6 | |
The Battle for Wesnoth | =1.3.1 | |
The Battle for Wesnoth | =1.3.2 | |
The Battle for Wesnoth | =1.3.3 | |
The Battle for Wesnoth | =1.3.4 | |
The Battle for Wesnoth | =1.3.5 | |
The Battle for Wesnoth | =1.3.6 | |
The Battle for Wesnoth | =1.3.7 | |
The Battle for Wesnoth | =1.3.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2007-3917 is classified as a moderate severity vulnerability.
To mitigate CVE-2007-3917, update to the latest version of the Wesnoth package that includes the fix.
CVE-2007-3917 can lead to invalid UTF-8 character handling on the client, potentially causing application crashes or unexpected behavior.
CVE-2007-3917 affects Wesnoth versions 1.2.0 through 1.3.8.
Yes, CVE-2007-3917 can be exploited remotely by sending a specially crafted long chat message.