dbcve.org
IrssiApplication

CVE-2007-4396

HIGH · 9.3 CVSS v2.0 Published 2007-08-18
Fix available
A fix is available. Upgrade to after 0.8.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Multiple CRLF injection vulnerabilities in (1) ixmmsa.pl 0.3, (2) l33tmusic.pl 2.00, (3) mpg123.pl 0.01, (4) ogg123.pl 0.01, (5) xmms.pl 2.0, (6) xmms2.pl 1.1.3, and (7) xmmsinfo.pl 1.1.1.1 scripts for irssi before 0.8.11 allow user-assisted remote attackers to execute arbitrary IRC commands via CRLF sequences 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 · high confidence

CRLF injection vulnerability in multiple irssi Perl scripts (ixmmsa.pl, l33tmusic.pl, mpg123.pl, ogg123.pl, xmms.pl, xmms2.pl, xmmsinfo.pl) before version 0.8.11. Attackers can embed CRLF sequences in .mp3 song metadata to inject arbitrary IRC commands when the file is played, allowing unauthorized IRC command execution.

MitigationUpgrade irssi to version 0.8.11 or later which includes fixed scripts, or manually patch the affected scripts to sanitize song names by filtering or escaping CRLF characters (%0D%0A) before processing.

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
IrssiApplication
Affected:<= 0.8.9

CVSS 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
Complete
Integrity
Complete
Availability
Complete

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed irssi version
    Run 'irssi --version' or check via package manager (dpkg -l irssi, rpm -q irssi)
    Affected if Version is 0.8.9 or lower
  2. Locate vulnerable Perl scripts
    Search for these files: ixmmsa.pl, l33tmusic.pl, mpg123.pl, ogg123.pl, xmms.pl, xmms2.pl, xmmsinfo.pl in ~/.irssi/scripts/ and /usr/share/irssi/scripts/
    Affected if Any of these scripts exist on the system
  3. Confirm scripts are loaded by irssi
    Check ~/.irssi/startup or ~/.irssi/scripts/autorun/ for autorun scripts, or run '/SCRIPT LIST' inside irssi
    Affected if Any of the vulnerable music scripts appear in the loaded scripts list
  4. Check script file timestamps or version comments
    Open the script files and look for version comments in the first few lines or check file modification date
    Affected if Script version is before 0.8.11 or no version patch is evident

You are affected if you are running irssi version 0.8.9 or lower with any of the listed music playback Perl scripts (ixmmsa.pl, l33tmusic.pl, mpg123.pl, ogg123.pl, xmms.pl, xmms2.pl, xmmsinfo.pl) loaded and actively used to play media files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.8.9
Interim mitigation

Upgrade irssi to version 0.8.11 or later which includes fixed scripts, or manually patch the affected scripts to sanitize song names by filtering or escaping CRLF characters (%0D%0A) before processing.

Recommended fix High confidence

Irssi 0.8.11 or later

  1. 1. Check current Irssi version by running: irssi --version
  2. 2. Upgrade Irssi to version 0.8.11 or later
  3. 3. On Debian/Ubuntu: sudo apt-get update && sudo apt-get install irssi
  4. 4. On RHEL/CentOS: sudo yum update irssi
  5. 5. On FreeBSD: sudo portupgrade irssi
  6. 6. Verify the upgrade was successful: irssi --version
  7. 7. Ensure upgraded version is 0.8.11 or higher
Caveat Minor - this is a stable release upgrade with bug fixes, but review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Irssi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4396 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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