CVE-2007-3322
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 4602 SW IP Phone (Model 4602D02A) with 2.2.2 and earlier SIP firmware uses a constant media port number for calls, which allows remote attackers to cause a denial of service (audio quality loss) via a flood of packets to the RTP port.
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 4602 SW IP Phone (Model 4602D02A) with SIP firmware 2.2.2 and earlier uses a predictable, constant RTP media port number for all calls. This design flaw allows remote attackers to easily flood the static RTP port with packets, causing denial of service through audio quality loss or complete audio disruption.
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
- 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.
-
Identify the device modelCheck the hardware label on the phone unit or query the device via SIP OPTIONS request to the phone's IP address, looking for model identification in the User-Agent or Server headersAffected if The device is not an Avaya 4602SW IP Phone (model 4602D02A)
-
Check the SIP firmware versionQuery the phone via its web administration interface or use SIP OPTIONS request to read the firmware version in the User-Agent or Server header fieldsAffected if The firmware version is 2.2 or earlier (r2.2 or below)
-
Verify RTP port behaviorMake a test call from the phone and observe the RTP source ports using network capture (tcpdump or Wireshark) on the network segment. Repeat several calls from different endpointsAffected if The RTP media ports remain constant across different calls (same port number used every time)
-
Confirm SIP firmware buildAccess the phone's web interface (http://<phone_ip>) and navigate to the about or status page to view the exact firmware build numberAffected if The build/revision shows r2.2 or lower (for example r2.1, r2.0)
The phone is affected if it is an Avaya 4602SW IP Phone running SIP firmware version 2.2 or earlier that uses a static/unchanging RTP port for every call.
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 phone firmware to a version newer than 2.2.2 which presumably implements dynamic port allocation, or implement network-level filtering/firewall rules to rate-limit or block excessive traffic to the RTP port range.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3322 — 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-3322 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