CVE-2006-0374
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 · uneditedAdvantage Century Telecommunication (ACT) P202S IP Phone 1.01.21 running firmware 1.1.21 has multiple undocumented ports available, which (1) might allow remote attackers to obtain sensitive information, such as memory contents and internal operating-system data, by directly accessing the VxWorks WDB remote debugging ONCRPC (aka wdbrpc) on UDP 17185, (2) reflect network data using echo (TCP 7), or (3) gain access without authentication using rlogin (TCP 513).
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 ACT P202S IP Phone firmware 1.1.21 contains multiple undocumented services exposing sensitive data: VxWorks WDB remote debugging (UDP 17185) allows memory/OS extraction, echo service (TCP 7) enables network data reflection, and rlogin (TCP 513) provides unauthenticated access. These debugging and legacy services should never be exposed on production networks.
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.01.21_firmware_1.1.21CVSS 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 the device modelAccess the device web interface, admin panel, or check physical labeling to confirm the device is an ACT P202S IP Phone from Advantage Century TelecommunicationAffected if The device model is ACT P202S or P202s from Advantage Century Telecommunication
-
Check the installed firmware versionAccess the device admin interface, web UI, or use SNMP to query the firmware version. Compare against the affected version 1.1.21Affected if Firmware version is exactly 1.1.21 (1.01.21_firmware_1.1.21)
-
Scan for open UDP port 17185Use a network port scanner (such as nmap) to probe the device for UDP port 17185: nmap -sU -p 17185 <device_ip>Affected if UDP port 17185 is open and responding, indicating VxWorks WDB debugging service is exposed
-
Scan for open TCP port 7Use a network port scanner to probe the device for TCP port 7: nmap -p 7 <device_ip>Affected if TCP port 7 is open, indicating the echo service is enabled and accessible
-
Scan for open TCP port 513Use a network port scanner to probe the device for TCP port 513: nmap -p 513 <device_ip>Affected if TCP port 513 is open, indicating the rlogin service is enabled and accessible
The device is affected if it is an ACT P202S IP Phone running firmware version 1.1.21 AND any of UDP port 17185, TCP port 7, or TCP port 513 are exposed on the 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 dataDisable or block access to UDP port 17185, TCP port 7, and TCP port 513 at the network perimeter; if available, apply vendor firmware updates to remove these undocumented services.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0374 — 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-2006-0374 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