CVE-1999-0672
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 · uneditedBuffer overflow in Fujitsu Chocoa IRC client via IRC channel topics.
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 · moderate confidenceBuffer overflow vulnerability in the Fujitsu Chocoa IRC client occurs when processing incoming IRC channel topics. When the client receives a topic string from the IRC server that exceeds the expected buffer length, it allows overwriting adjacent memory, potentially enabling arbitrary code execution.
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.0beta7rCVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/A:P
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.
-
Locate Fujitsu Chocoa IRC client installationSearch system for files or directories named 'Chocoa', 'chocoa', or check standard installation paths for legacy IRC clients. On Unix systems, check /usr/local, /opt, or home directories. On Windows, check Program Files folders.Affected if Fujitsu Chocoa client is found installed on the system
-
Identify installed versionExamine version information in the executable, any accompanying version files, or check the binary metadata. The affected version is specifically 1.0beta7r.Affected if Installed version is Fujitsu Chocoa 1.0beta7r
-
Verify IRC client is active or configuredCheck if the Chocoa client has been launched or configured with server connections. Look for configuration files in the client directory that contain IRC server details or channel settings.Affected if The client has been used or configured to connect to IRC servers
-
Confirm topic handling is enabledThe vulnerability triggers when the client processes incoming channel topics from an IRC server. Determine if the client has joined any channels or has auto-join functionality configured.Affected if The client has joined or auto-joins IRC channels where topics are received
A user is affected if Fujitsu Chocoa IRC client version 1.0beta7r is installed and has been used to connect to IRC channels, as the buffer overflow occurs when processing incoming channel topics that exceed the expected buffer length.
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 dataIf the Chocoa IRC client remains in use, implement input length validation on topic processing routines or migrate to a maintained IRC client. For legacy systems, restrict network exposure and monitor for exploitation attempts.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0672 — 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-1999-0672 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