Skip to main content
Mallory
HighVulnerability

CVE-2005-1702: Format String Vulnerability in Warrior Kings Series

Published May 24, 2005 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS4.8%92nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Black Cactus
IdentifiersCVE-2005-1702CWE-134

A format string vulnerability exists in Warrior Kings: Battles 1.23 and earlier and Warrior Kings 1.3 and earlier. The vulnerability is triggered when user-supplied input, specifically a nickname, is processed without proper sanitization, allowing format string specifiers to be interpreted by the application. This can lead to arbitrary code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote attackers can exploit this vulnerability to execute arbitrary code on the affected system, potentially leading to full compromise of the game client or server, depending on the context in which the vulnerable code is executed.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to trusted users, monitor for suspicious activity, and use input validation or filtering to prevent format string specifiers in nicknames. Employ host-based intrusion prevention systems to detect exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of Warrior Kings: Battles and Warrior Kings that properly sanitizes user input and does not pass unsanitized strings to format functions. If no patch is available, consider disabling nickname functionality or restricting input to safe characters only.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Black CactusWarrior Kingsapplication
Black CactusWarrior Kings Battlesapplication
FAQ

Frequently asked questions

Is CVE-2005-1702 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2005-1702 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2005-1702?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2005-1702. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2005-1702?
Upgrade to a patched version of Warrior Kings: Battles and Warrior Kings that properly sanitizes user input and does not pass unsanitized strings to format functions. If no patch is available, consider disabling nickname functionality or restricting input to safe characters only.
What products are affected by CVE-2005-1702?
Black Cactus Warrior Kings and Black Cactus Warrior Kings Battles.
How severe is CVE-2005-1702?
CVE-2005-1702 has a CVSS v2 score of 7.5 (High) and an EPSS score of 4.8% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.