CVE-2007-3436
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 · uneditedMicrosoft MSN Messenger 4.7 on Windows XP allows remote attackers to cause a denial of service (resource consumption) via a flood of SIP INVITE requests to the port specified for voice conversation.
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 confidenceMicrosoft MSN Messenger 4.7 on Windows XP contains a denial of service vulnerability where the application fails to properly handle excessive SIP INVITE requests directed at the voice conversation port, allowing remote attackers to consume resources and render the service unresponsive.
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= 4.7CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check the Windows versionOpen a command prompt and run 'winver' or check System Properties. Alternatively, run 'systeminfo' in cmd and look for 'OS Name' and 'OS Version'.Affected if The system is running Windows XP (any version)
-
Verify MSN Messenger 4.7 installationCheck for the presence of msnmsgr.exe in the installation directory. Common paths: C:\Program Files\MSN Messenger\msnmsgr.exe or C:\Program Files\Windows Live\msnmsgr.exe. You can also check the Windows Registry under HKLM\SOFTWARE\Microsoft\MSN Messenger or look in Add/Remove Programs.Affected if Microsoft MSN Messenger version 4.7 is installed on the system
-
Confirm the exact version numberRight-click on msnmsgr.exe (if found), select Properties, then go to the Details tab to view the File Version. Alternatively, run 'msnmsgr.exe /version' or check the registry value at HKLM\SOFTWARE\Microsoft\MSN Messenger\InstallPath for the version entry.Affected if The installed version is exactly 4.7 (note: other versions like 4.6, 4.5, or 6.x are NOT affected by this specific CVE)
-
Check if voice conversation feature could be activeMSN Messenger 4.7 included built-in voice conversation capability using SIP protocol on ports 6891-6901 (default range). Check if Windows Firewall or any personal firewall has exceptions for MSN Messenger, or if the application is configured to allow incoming voice connections.Affected if The voice/SIP functionality is enabled or allowed through firewall exceptions, making the service reachable on the voice ports
You are affected only if you are running Windows XP with Microsoft MSN Messenger version 4.7 exactly, and the voice conversation feature is enabled or accessible (the application listens for incoming SIP INVITE 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 dataImplement network-level filtering or firewall rules to rate-limit or block inbound SIP INVITE requests, or migrate to a supported modern messaging platform as MSN Messenger and Windows XP are obsolete and no longer receive security updates.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3436 — 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-3436 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