CVE-2002-1675
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 · uneditedFormat string vulnerability in the Cio_PrintF function of cio_main.c in Unreal IRCd 3.1.1 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via format string specifiers.
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 confidenceUnreal IRCd 3.1.1 contains a format string vulnerability in the Cio_PrintF function of cio_main.c. The vulnerability occurs when user-controlled input is passed directly to a format function (e.g., printf) without proper sanitization, allowing attackers to inject format specifiers (%s, %n, etc.) to read from or write to stack memory, potentially leading to crash or 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= 3.1.1CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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.
-
Identify Unreal IRCd installation and versionRun command to check installed Unreal IRCd version, such as: unrealircd -v, ./unreal -v, or check package manager listing (dpkg -l, rpm -qa)Affected if Displayed version is exactly 3.1.1
-
Locate the Unreal IRCd binary or sourceFind the running Unreal IRCd process or executable using: ps aux | grep ircd, which unrealircd, or locate the installation directoryAffected if The binary or source files exist and version verification shows 3.1.1
-
Check if the vulnerable function existsExamine the cio_main.c source file or compiled binary for the Cio_PrintF function using: grep -r Cio_PrintF in source, or strings binary | grep Cio_PrintFAffected if The Cio_PrintF function is present in the binary/source and version is 3.1.1
-
Verify service is runningCheck if Unreal IRCd daemon is active using: ps aux | grep -i unreal, netstat -tlpn | grep ircd, or systemctl status unrealircdAffected if The service is running and version is confirmed as 3.1.1
The system is affected if Unreal IRCd version 3.1.1 is installed and running, as this exact version contains the format string vulnerability in Cio_PrintF.
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 to a patched version of Unreal IRCd that addresses this vulnerability, or apply a code fix to use proper format string arguments (e.g., printf("%s", user_input) instead of printf(user_input)).
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1675 — 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-2002-1675 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