CVE-2007-3917
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 truncate_message function in server/server.cpp. NOTE: this issue affects both clients and servers.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Wesnoth multiplayer engine fails to properly handle truncation of messages containing multibyte characters. When a long message with multibyte characters is truncated, it can produce an invalid UTF-8 string that triggers an uncaught exception in the truncate_message function, causing the client or server to crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.2= 1.2.1= 1.2.2= 1.2.3= 1.2.4= 1.2.5= 1.2.6= 1.3.1= 1.3.2= 1.3.3= 1.3.4= 1.3.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Wesnoth versionRun 'wesnoth --version' or check the program's 'About' menu in the game client. On Linux, also try 'dpkg -l battle-for-wesnoth' or 'rpm -qi battle-for-wesnoth' if installed via package manager.Affected if The version matches one of these: 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.3.1, 1.3.2, 1.3.3, 1.3.4, or 1.3.5
-
Verify multiplayer functionality is in useConfirm whether the Wesnoth client connects to multiplayer servers or hosts networked games. Check if the 'Multiplayer' menu option is accessible or if network game logs exist.Affected if Multiplayer mode is enabled or the client has connected to multiplayer servers
-
Identify message handling in multiplayer sessionsReview any available debug logs or network traffic captures for multiplayer chat messages. The vulnerability triggers when long messages containing multibyte (non-ASCII) characters are received and processed by the truncate_message function.Affected if Multiplayer sessions involve chat messages with multibyte characters being transmitted
You are affected if your installed Wesnoth version is 1.2 through 1.2.6, 1.3.1 through 1.3.5, and you use the multiplayer functionality where multibyte character messages can be received from other players.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Wesnoth to version 1.2.7 or later for the 1.2 branch, or 1.3.9 or later for the 1.3 branch. If upgrading is not immediately possible, consider restricting network connections to trusted servers.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3917 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-3917 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data