CVE-2007-3369
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 · uneditedBuffer overflow in the Polycom SoundPoint IP 601 SIP phone with BootROM 3.0.x+ and SIP version 1.6.3.0067 allows remote attackers to cause a denial of service (device hang or reboot) via an INVITE message with a long Via header.
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 confidenceBuffer overflow vulnerability in Polycom SoundPoint IP 601 SIP phones (BootROM 3.0.x+ and SIP version 1.6.3.0067) allows remote attackers to cause denial of service by sending specially crafted INVITE messages with an excessively long Via header, resulting in device hang or reboot.
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= 1.6.3.0067_bootrom_3.0.0CVSS 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.
-
Identify the device modelAccess the phone's web interface or check the device label to confirm it is a Polycom SoundPoint IP 601 modelAffected if Device is not a Polycom SoundPoint IP 601, the check does not apply
-
Check SIP firmware versionLog into the phone's web interface and navigate to the Status or About page to view the SIP software versionAffected if SIP firmware version is 1.6.3.0067
-
Check BootROM versionAccess the phone's boot menu or web interface to determine the BootROM version (look for version 3.0.x or higher)Affected if BootROM version is 3.0.x or higher (specifically 3.0.0 in the known affected build)
-
Confirm SIP service is enabledCheck the phone's SIP configuration settings to confirm SIP protocol is actively configured and registeredAffected if SIP is enabled and configured on the device (the vulnerability requires SIP to be running to process the malicious INVITE)
-
Assess network exposure of SIP serviceReview firewall rules and network configuration to determine if SIP ports are accessible from untrusted or external networksAffected if SIP service is exposed to untrusted network segments (exploitation requires receiving the malicious INVITE from network)
Device is affected if it is a Polycom SoundPoint IP 601 running SIP version 1.6.3.0067 with BootROM 3.0.0, has SIP enabled, and can receive SIP traffic from an attacker (even local network).
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 SIP firmware to a patched version if available; alternatively, implement network-level filtering to restrict SIP traffic from untrusted sources to mitigate exploitation.
- 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-3369 — 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-3369 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