CVE-1999-1351
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 · uneditedDirectory traversal vulnerability in KVIrc IRC client 0.9.0 with the "Listen to !nick <soundname> requests" option enabled allows remote attackers to read arbitrary files via a .. (dot dot) in a DCC GET request.
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 confidenceDirectory traversal vulnerability in KVIrc IRC client 0.9.0 allows remote attackers to read arbitrary files via '..' sequences in DCC GET requests when the 'Listen to !nick <soundname> requests' option is enabled.
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= 0.9.0CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 KVIrc installation and versionLocate the KVIrc executable or check system for installed software. Common locations on Windows: C:\Program Files\KVIrc\kvirc.exe. On Linux/Unix: check /usr/bin/kvirc or ~/.kvirc. Use command 'kvirc --version' or check the program's About/Help section to confirm version number is exactly 0.9.0Affected if KVIrc version 0.9.0 is installed and running
-
Check if DCC GET is enabledIn KVIrc 0.9.0, DCC (Direct Client Communication) functionality is typically configured in Settings > DCC Options or Settings > File Transfers. Look for any enabled DCC receiving optionsAffected if DCC GET or file receiving is enabled in KVIrc settings
-
Verify the 'Listen to !nick <soundname> requests' optionAccess KVIrc settings: Navigate to Settings > Sound Events or Settings > DCC Options. Locate the specific option labeled 'Listen to !nick <soundname> requests'. This is a specific sound request handling feature that processes DCC requests from other users. Check if this checkbox is ticked or enabledAffected if The 'Listen to !nick <soundname> requests' option is enabled in KVIrc configuration
User is affected if KVIrc version 0.9.0 is installed AND the 'Listen to !nick <soundname> requests' option is enabled, as this combination allows remote attackers to trigger directory traversal via DCC GET requests
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 dataDisable the 'Listen to !nick <soundname> requests' option in KVIrc settings, or upgrade to a patched version if available.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1351 — 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-1351 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