Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2004-1208: Buffer Overflow in Orbz 2.10 Join Request Password Field

Published Dec 15, 2004 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS7.6%95th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
21-6 Productions
IdentifiersCVE-2004-1208CWE-120

A buffer overflow vulnerability exists in Orbz 2.10 and earlier, where the application fails to properly validate the length of the password field in a join request. This allows a remote attacker to send an overly long password, causing a buffer overflow and potentially enabling arbitrary code execution or a denial of service (application crash).

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 can result in remote code execution with the privileges of the Orbz process, or a denial of service by crashing the application. This could allow an attacker to take control of the affected system or disrupt service availability.

Mitigation

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

Restrict network access to the Orbz service to trusted hosts only. Employ network-level filtering to block untrusted sources. Monitor for abnormal application crashes and consider using host-based intrusion prevention systems to detect exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of Orbz that properly validates the length of the password field in join requests. If no patch is available, consider discontinuing use of the affected software.

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
21-6 ProductionsOrbzapplication
FAQ

Frequently asked questions

Is CVE-2004-1208 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2004-1208 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2004-1208?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2004-1208.
Is there a patch for CVE-2004-1208?
Upgrade to a patched version of Orbz that properly validates the length of the password field in join requests. If no patch is available, consider discontinuing use of the affected software.
What products are affected by CVE-2004-1208?
21-6 Productions Orbz.
How severe is CVE-2004-1208?
CVE-2004-1208 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 7.6% (95th 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.