CVE-2007-3350
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 · uneditedAOL Instant Messenger (AIM) 6.1.32.1 on Windows XP allows remote attackers to cause a denial of service (application hang) via a flood of spoofed SIP INVITE requests.
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 confidenceAOL Instant Messenger 6.1.32.1 on Windows XP contains a vulnerability in its SIP (Session Initiation Protocol) handling implementation. Remote attackers can cause the application to hang and become unresponsive by flooding the target system with spoofed SIP INVITE requests. The application does not properly handle the rapid influx of malformed or spoofed session initiation messages, leading to resource exhaustion and denial of service.
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= 6.1.32.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
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify AIM installationCheck if AOL Instant Messenger is installed on the system by looking in Program Files for the AIM folder, or checking Add/Remove Programs for an entry named 'AOL Instant Messenger'Affected if AIM is not installed on the system
-
Check installed versionLocate the AIM executable (aim.exe) in the installation directory, right-click and view Properties, or run 'aim.exe -version' from command line if supported. Common paths: C:\Program Files\AOL Instant Messenger\Affected if The version is exactly 6.1.32.1 - any other version is not affected by this specific CVE
-
Confirm SIP functionality is enabledOpen AIM, go to Menu > Settings > Preferences, and look for SIP, Voice Chat, or Phone settings. Check if the 'Enable voice' or 'Enable SIP' option is checked or availableAffected if The SIP or voice chat feature is enabled - this vulnerability only applies when AIM's SIP handling code is active
-
Verify network exposureCheck if the system has UDP port 5060 (SIP) or related RTP media ports open and reachable from untrusted networks, or if AIM is configured to accept incoming voice callsAffected if The system can receive unsolicited SIP INVITE packets from the network
A system is affected only if AOL Instant Messenger version 6.1.32.1 is installed with the SIP/voice chat feature enabled and exposed to network SIP traffic.
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 dataGiven that AIM is largely discontinued, the primary mitigation is to migrate away from AIM to modern instant messaging platforms. If continued use is required, network-level filtering of SIP traffic at the perimeter or host-based firewall rules to block unsolicited SIP INVITE packets can provide interim protection against this DoS vector.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3350 — 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-3350 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