Skip to content
Noroxi
CVE-2010-2452· NVD / CVE Program· CNA mitre

Directory traversal vulnerability in the DCC functionality in KVIrc 3.4 and 4.0 allows remote attackers to overwrite arbitrary files via unk

Directory traversal vulnerability in the DCC functionality in KVIrc 3.4 and 4.0 allows remote attackers to overwrite arbitrary files via unknown vectors.

CriticalCVSS 9.3 · v2.0—No exploit Fix available
Published
Jun 29, 2010
Updated
Jun 16, 2026
EPSS
4.1% · 90th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

38

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.1%

Affected systems

VendorProduct
kvirckvirc

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • kvirc kvirc3.4.0
  • kvirc kvirc4.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12kvircbefore 4:4.0.0~svn4340+rc3-14:4.0.0~svn4340+rc3-1
Debian:5.0kvircbefore 2:3.4.0-52:3.4.0-5

Other highest-scoring records for the same primary product.

  • CVE-2010-2451Multiple format string vulnerabilities in the DCC functionality in KVIrc 3.4 and 4.0 have unspecified impact and remote attack vectors.
    41Plan
  • CVE-2008-7070Argument injection vulnerability in the URI handler in KVIrc 3.4.2 Shiny allows remote attackers to execute arbitrary commands via a " (quot
    39Monitor
  • CVE-2008-4748Format string vulnerability in the URI handler in KVirc 3.4.0, when set as the default application for processing IRC URIs, allows remote at
    32Monitor
  • CVE-2010-2785The IRC Protocol component in KVIrc 3.x and 4.x before r4693 does not properly handle \ (backslash) characters, which allows remote authenti
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:kvirc4:4.0.0~svn4340+rc3-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    C · data can be read
    Integrity
    C · data or configuration can be modified
    Availability
    C · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    C
    Integrity impact
    C
    Availability impact
    C

    CVSS vector

    AV:N/AC:M/Au:N/C:C/I:C/A:C

    nvd-primary

    Root cause

    A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    const file = path.join(ROOT, req.query.name);res.sendFile(file);

    Fixed

    ts
    const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records