CVE-2007-3319
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 · uneditedThe Avaya 4602SW IP Phone (Model 4602D02A) with 2.2.2 and earlier SIP firmware does not use the cnonce parameter in the Authorization header of SIP requests during MD5 digest authentication, which allows remote attackers to conduct man-in-the-middle attacks and hijack or intercept communications.
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 confidenceThe Avaya 4602SW IP Phone with SIP firmware 2.2.2 and earlier omits the cnonce parameter in the Authorization header during MD5 digest authentication, violating the SIP authentication specification and enabling replay attacks that allow man-in-the-middle attackers to hijack or intercept communications.
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= r2.2CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify Avaya 4602SW IP Phone on the networkScan the network for devices responding on SIP port 5060/UDP and check for HTTP management interface (port 80) or SNMP endpoints that show Avaya 4602SW as the device manufacturerAffected if The device is an Avaya 4602SW IP Phone with SIP firmware 2.2.2 or earlier
-
Determine the installed SIP firmware versionAccess the phone's web management interface or use SNMP to query the device firmware version; compare against the affected range (2.2.2 and earlier for r2.2 release)Affected if The firmware version is 2.2.2 or earlier, or any version within the r2.2 release line
-
Verify SIP digest authentication is enabledCheck the phone's SIP configuration settings via the web interface or config file to confirm MD5 digest authentication is active for SIP registration or callsAffected if SIP digest authentication is enabled and the phone is registering to a SIP proxy/registrar
-
Capture SIP traffic and inspect Authorization headerUse a network sniffer (such as tcpdump or Wireshark) to capture SIP REGISTER or INVITE packets sent by the phone; examine the Authorization or Proxy-Authorization header for the presence of the cnonce parameterAffected if The Authorization header is present but lacks the cnonce field, indicating non-compliant digest authentication
The environment is affected if an Avaya 4602SW IP Phone is running SIP firmware 2.2.2 or earlier with digest authentication enabled, and captured SIP traffic shows Authorization headers missing the cnonce parameter.
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 dataUpgrade the Avaya 4602SW IP Phone firmware to a version newer than 2.2.2 that properly implements cnonce in SIP digest authentication, and verify the fix in a test environment before production deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3319 — 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-3319 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