CVE-2007-3533
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 3Com IntelliJack Switch NJ220 before 2.0.23 allows remote attackers to cause a denial of service (reboot and reporting outage) via a loopback packet with zero in the length field.
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 confidenceThe 3Com IntelliJack Switch NJ220 before version 2.0.23 is vulnerable to a denial-of-service attack. Remote attackers can send specially crafted loopback packets containing a zero value in the length field, causing the switch to reboot and report an outage.
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<= 2.0.22CVSS 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.
-
Confirm device model is 3Com IntelliJack Switch NJ220Access the device management interface (web UI, console, or CLI) and verify the model number displays as 3cnj220 or 3Com IntelliJack Switch NJ220Affected if The device is not a 3Com IntelliJack Switch NJ220 - this CVE does not apply to other models
-
Retrieve the installed firmware versionLog into the device management interface or CLI and locate the firmware/version information, typically found under System Info, Device Status, or similar diagnostic sectionAffected if Unable to determine firmware version - manual inspection of device label or documentation may be required
-
Compare firmware version to affected rangeExamine the firmware version string found in the previous step; versions are formatted as major.minor.build (e.g., 2.0.22)Affected if Firmware version is 2.0.22 or lower (e.g., 2.0.21, 2.0.20, 1.x.x) - device is vulnerable; version 2.0.23 or higher is not affected
-
Verify network accessibility of the deviceConfirm the device has an active IP address and is reachable on the network segment where untrusted traffic could be receivedAffected if Device is not network-accessible - while still technically affected if running a vulnerable version, the attack surface is reduced
A user is affected if they are running 3Com IntelliJack Switch NJ220 firmware version 2.0.22 or lower, and the device is network-accessible to receive the specially crafted loopback packets.
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 3Com IntelliJack Switch NJ220 firmware to version 2.0.23 or later. As a compensating control, implement network segmentation and access controls to limit exposure to untrusted network segments.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.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 $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3533 — 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-3533 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