CVE-2019-3928
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 · uneditedCrestron AM-100 with firmware 1.6.0.2 and AM-101 with firmware 2.7.0.2 allow any user to obtain the presentation passcode via the iso.3.6.1.4.1.3212.100.3.2.7.4 OIDs. A remote, unauthenticated attacker can use this vulnerability to access a restricted presentation or to become the presenter.
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 Crestron AM-100 and AM-101 wireless presentation devices expose the presentation passcode through an unprotected SNMP OID (iso.3.6.1.4.1.3212.100.3.2.7.4). A remote, unauthenticated attacker can retrieve this OID value without any credentials to gain access to restricted presentations or hijack the presenter role.
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.6.0.2= 2.7.0.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify the device model on the networkScan the network for devices with vendor OUI matching Crestron (00:1D:9C) or check the web interface/HTTP banner for AM-100 or AM-101 presentation systemAffected if The device is a Crestron AM-100 or AM-101 wireless presentation device
-
Verify SNMP service is accessibleUse an SNMP scanner or snmpwalk against the device IP with community string 'public' or 'private', or check if UDP port 161 is openAffected if SNMP responds to queries without authentication (no credentials required)
-
Query the vulnerable OID for passcode exposureRun snmpget or snmpwalk on OID iso.3.6.1.4.1.3212.100.3.2.7.4 against the device using no authentication or default community stringsAffected if The OID returns a value (the presentation passcode) without requiring any credentials
-
Check the installed firmware versionAccess the device web interface and navigate to Settings > Info, or use SNMP to query the firmware version OID, and compare to the affected versionsAffected if Firmware version is 1.6.0.2 (AM-100) or 2.7.0.2 (AM-101)
A user is affected if they have a Crestron AM-100 or AM-101 device with SNMP accessible on the network and the specific OID returns the presentation passcode without authentication, particularly on the listed firmware versions.
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 dataRestrict SNMP access to the device via firewall rules or VLAN segmentation; if available, apply vendor firmware updates that address this information disclosure; alternatively, consider network isolation of presentation devices from untrusted networks.
- 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-2019-3928 — 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-2019-3928 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