CVE-2007-4402
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 · uneditedMultiple unspecified scripts in mIRC allow user-assisted remote attackers to execute arbitrary code via the '|' (pipe) shell metacharacter in the name of the song in a .mp3 file.
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 confidencemIRC contains multiple scripts that process .mp3 file metadata (song names/ID3 tags). These scripts fail to sanitize the pipe ('|') shell metacharacter from the song name field, allowing arbitrary command execution when the client processes the maliciously crafted mp3 file.
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= 2.49CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Verify mIRC versionCheck the installed mIRC version by opening mIRC and looking at the title bar, or right-clicking the mIRC icon and selecting 'Properties' to view version informationAffected if The version is exactly 2.49
-
Identify custom script filesLook for .mrc or .ini script files in the mIRC directory that contain code for processing .mp3 files or ID3 tags (search for strings like 'mp3', 'ID3', or file handling routines)Affected if Custom scripts exist that parse .mp3 file metadata or ID3 tags
-
Check for pipe character handling in scriptsExamine any .mrc script files for commands that read or process song name fields from .mp3 files without sanitizing special charactersAffected if Scripts read ID3 tag fields (especially song title/artist) and pass them to shell commands without filtering the pipe (|) character
-
Inspect automatic trigger mechanismsReview script aliases that automatically process files upon receiving or downloading them, looking for on FILESERVER, on GET, or on DOWNLOAD event handlers that invoke .mp3 processing routinesAffected if mIRC is configured to automatically process downloaded .mp3 files through custom scripts that parse metadata
A user is affected if they run mIRC version 2.49 with custom scripts that automatically parse .mp3 file metadata (ID3 tags) and fail to sanitize the pipe character before passing data to shell commands.
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 dataUpdate mIRC to a patched version (post-2007 releases contain fixes). Avoid opening or playing .mp3 files from untrusted sources, as the vulnerability is triggered when mIRC scripts parse the file's metadata.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4402 — 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-2007-4402 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