Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2024-25004: Stack-based Buffer Overflow in KiTTY (username handling)

Published Feb 9, 2024 · 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.8High · v3.1
EPSS1.8%79th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
9bis
IdentifiersCVE-2024-25004CWE-121

A stack-based buffer overflow vulnerability exists in KiTTY versions 0.76.1.13 and earlier, specifically in the handling of the username input (at line 2600). The vulnerability is due to insufficient bounds checking and lack of input sanitization, allowing an attacker to supply an overly long username and overwrite adjacent stack memory, potentially leading 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.

Successful exploitation allows an attacker to execute arbitrary code in the context of the affected process. This could lead to full compromise of the system running KiTTY, depending on the privileges of the process.

Mitigation

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

As a temporary mitigation, restrict access to the application to trusted users only, and avoid using untrusted or attacker-controlled input for the username field. Employ host-based intrusion prevention systems to detect and block exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade to a version of KiTTY later than 0.76.1.13 in which this vulnerability has been patched. Ensure that all input handling, especially for user-supplied data such as usernames, includes proper bounds checking and input validation.

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
9bisKittyapplication
FAQ

Frequently asked questions

Is CVE-2024-25004 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2024-25004 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-25004?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2024-25004.
Is there a patch for CVE-2024-25004?
Upgrade to a version of KiTTY later than 0.76.1.13 in which this vulnerability has been patched. Ensure that all input handling, especially for user-supplied data such as usernames, includes proper bounds checking and input validation.
What products are affected by CVE-2024-25004?
9bis Kitty.
How severe is CVE-2024-25004?
CVE-2024-25004 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 1.8% (79th 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.