CVE-2020-3932
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 · uneditedA vulnerable SNMP in Draytek VigorAP910C cannot be disabled, which may cause information leakage.
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 Draytek VigorAP910C access point has an SNMP service that cannot be disabled through the administrative interface. This configuration flaw allows potential attackers to query SNMP for sensitive system information including device configuration, network topology, and potentially credentials if default community strings are used.
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.3.1CVSS 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.
-
Verify device modelAccess the device web interface or use SNMP to query the device sysDescr or sysObjectID to confirm the device is a Draytek VigorAP910C access pointAffected if Device is a VigorAP910C
-
Check firmware versionNavigate to the device admin interface (typically at 192.168.1.1) and check the firmware version in the system status or firmware upgrade section, or query via SNMP sysDescr if accessibleAffected if Firmware version equals 1.3.1
-
Confirm SNMP service is activeAttempt an SNMP query against the device IP using snmpwalk or snmpget with community string 'public' (default) on UDP port 161Affected if SNMP query returns responses containing system information such as sysDescr, sysContact, or interface statistics
-
Verify SNMP community stringsCheck the SNMP configuration page in the device web interface under SNMP settings, or attempt queries with common default community strings including 'public', 'private', and 'draytek'Affected if Default community strings are in use or SNMP configuration shows community strings have not been changed from vendor defaults
User is affected if the device is a VigorAP910C running firmware version 1.3.1 with SNMP service enabled and responding to queries, especially with default or weak community strings.
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 dataSince SNMP cannot be disabled on the affected device, implement compensating controls: restrict network access to the management interface via firewall rules or VLAN segmentation, change default SNMP community strings to non-guessable values, and monitor for unauthorized SNMP queries. Consider firmware updates if the vendor releases a patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3932 — 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-2020-3932 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