CVE-2005-3716
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 SNMP daemon in UTStarcom F1000 VOIP WIFI Phone s2.0 running VxWorks 5.5.1 with kernel WIND 2.6 has hard-coded public credentials that cannot be changed, which allows attackers to obtain sensitive information.
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 SNMP daemon in UTStarcom F1000 VOIP WIFI Phone running VxWorks 5.5.1 contains hard-coded SNMP community strings (public credentials) embedded in the firmware that cannot be modified by administrators. Attackers with network access to the SNMP service can use these static credentials to authenticate and retrieve sensitive device information including configuration, status, and potentially voice traffic metadata.
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.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 UTStarcom F1000Check the device label, web interface, or SNMP sysDescr OID (.1.3.6.1.2.1.1.1.0) to verify the device is specifically the F1000 WiFi phoneAffected if Device is not an F1000 model - different products are not affected by this CVE
-
Verify firmware version is 2.0Access the device web interface, check system information via SNMP, or inspect firmware binary. The affected version is specifically firmware = 2.0Affected if Firmware version is not 2.0 - other versions may have different behavior or fixes
-
Determine if SNMP service is enabledCheck device configuration settings via web interface or attempt an SNMP query to UDP port 161. If SNMP responds, the service is enabledAffected if SNMP service is disabled on the device - the vulnerability cannot be exploited if SNMP is not running
-
Check SNMP network accessibilityTest UDP port 161 connectivity from external networks. Verify if the device SNMP port is exposed to untrusted networks or only to trusted management segmentsAffected if SNMP is accessible from untrusted networks - hard-coded credentials can be exploited by anyone with network access
You are affected only if you have an F1000 device running firmware 2.0 with SNMP service enabled and accessible from a network where attackers could reach UDP port 161.
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 the SNMP service if not required, or restrict network access to UDP port 161 using firewall rules to prevent unauthorized external access. Since the credentials cannot be changed, contact the vendor for firmware updates or consider replacing the device if SNMP is operationally required.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3716 — 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-2005-3716 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