dbcve.org
4602sw Ip PhoneHardware / appliance · Avaya

CVE-2007-3321

MEDIUM · 5.0 CVSS v2.0 Published 2007-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Avaya 4602 SW IP Phone (Model 4602D02A) with 2.2.2 and earlier SIP firmware allows remote attackers to cause a denial of service (device reboot) via a flood of packets to the BOOTP port (68/udp).

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 confidence

The Avaya 4602 SW IP Phone (Model 4602D02A) with SIP firmware version 2.2.2 and earlier contains a denial of service vulnerability where a flood of UDP packets to port 68 (BOOTP) causes the device to reboot, rendering the phone unavailable.

MitigationImplement network-level controls such as firewall rules or rate-limiting on UDP port 68 to restrict BOOTP traffic, or upgrade to a patched firmware version if available.

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
4602sw Ip PhoneHardware / appliance
Affected:<= r2.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the physical phone or check network inventory for Avaya 4602 SW IP Phone (model 4602D02A)
    Affected if The device is not an Avaya 4602 SW IP Phone, the check does not apply
  2. Check the SIP firmware version
    Access the phone's web interface or admin menu and locate the firmware version information, typically under 'Status' or 'Software Version'
    Affected if Firmware version is r2.2 or earlier, or version 2.2.2 or earlier
  3. Verify UDP port 68 accessibility
    From a network host, run 'nc -zvu <phone_ip> 68' or use nmap to check if UDP port 68 is open and reachable
    Affected if UDP port 68 responds to external traffic or shows as open/filtered
  4. Check BOOTP client configuration
    Access the phone's admin interface and verify if BOOTP/DHCP client is enabled in the network settings
    Affected if BOOTP client is enabled and the phone requests IP configuration via BOOTP on port 68

User is affected if they have an Avaya 4602 SW IP Phone running firmware r2.2 or earlier with UDP port 68 accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network-level controls such as firewall rules or rate-limiting on UDP port 68 to restrict BOOTP traffic, or upgrade to a patched firmware version if available.

Fix this in 4602sw Ip Phone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-3321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-3321 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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