dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 6 May 2022.
Am 100 FirmwareOperating system · Crestron

CVE-2019-3929

CRITICAL · 9.8 CVSS v3.1 Published 2019-04-30
Fix available
A fix is available. Upgrade to 2.4.1.19 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

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 · unedited
The Crestron AM-100 firmware 1.6.0.2, Crestron AM-101 firmware 2.7.0.1, Barco wePresent WiPG-1000P firmware 2.3.0.10, Barco wePresent WiPG-1600W before firmware 2.4.1.19, Extron ShareLink 200/250 firmware 2.0.3.4, Teq AV IT WIPS710 firmware 1.1.0.7, SHARP PN-L703WA firmware 1.4.2.3, Optoma WPS-Pro firmware 1.0.0.5, Blackbox HD WPS firmware 1.0.0.5, InFocus LiteShow3 firmware 1.0.16, and InFocus LiteShow4 2.0.0.7 are vulnerable to command injection via the file_transfer.cgi HTTP endpoint. A remote, unauthenticated attacker can use this vulnerability to execute operating system commands as root.

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 confidence

Multiple wireless presentation system devices contain a command injection vulnerability in the file_transfer.cgi HTTP endpoint. The vulnerability allows a remote, unauthenticated attacker to inject and execute arbitrary operating system commands with root privileges due to insufficient input sanitization in the web interface.

MitigationApply available vendor firmware updates. If patches are unavailable, network-segment devices behind firewalls, disable remote management interfaces, and implement strict input validation at network boundaries.

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
Am 100 FirmwareOperating system
Affected:= 1.6.0.2
Am 101 FirmwareOperating system
Affected:= 2.7.0.2
Wepresent Wipg 1000p FirmwareOperating system
Affected:= 2.3.0.10
Wepresent Wipg 1600w FirmwareOperating system
Affected:< 2.4.1.19
Sharelink 200 FirmwareOperating system
Affected:= 2.0.3.4
Sharelink 250 FirmwareOperating system
Affected:= 2.0.3.4
Wips710 FirmwareOperating system
Affected:= 1.1.0.7
Pn L703wa FirmwareOperating system
Affected:= 1.4.2.3

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device admin interface or check the device label/packaging to confirm the exact model (Crestron AM-100, AM-101, Barco wePresent WiPG series, Extron ShareLink 200/250, Teqavit Wips710, Sharp Pn L703wa)
    Affected if The device is one of the models listed in the affected products list
  2. Determine firmware version
    Log into the device web interface and navigate to the About/System Info/Status page to find the installed firmware version, or use SNMP or the device serial console if available
    Affected if The firmware version matches exactly (for = versions) or falls below the threshold (for < versions) as specified in the affected products list (AM-100: 1.6.0.2, AM-101: 2.7.0.2, WiPG 1000p: 2.3.0.10, WiPG 1600w: < 2.4.1.19, ShareLink 200/250: 2.0.3.4, Wips710: 1.1.0.7, Pn L703wa: 1.4.2.3)
  3. Verify file_transfer.cgi endpoint exists
    Send an HTTP GET or POST request to http://[device-ip]/cgi-bin/file_transfer.cgi and check for a valid HTTP response (the endpoint exists on affected devices)
    Affected if The endpoint returns a valid response (indicating the vulnerable CGI script is present)
  4. Check network exposure
    Review firewall rules, ACLs, and network segmentation to determine if the device management interface and file_transfer.cgi endpoint are accessible from untrusted networks
    Affected if The device and file_transfer.cgi endpoint are accessible from untrusted/non-segmented network segments (the vulnerability is exploitable by unauthenticated remote attackers)

Your environment is affected if you have one of the listed device models running the specified vulnerable firmware version and the file_transfer.cgi endpoint is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2.4.1.19 or later
Fixed in 2.4.1.19
Interim mitigation

Apply available vendor firmware updates. If patches are unavailable, network-segment devices behind firewalls, disable remote management interfaces, and implement strict input validation at network boundaries.

Fix this in Am 100 Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3929 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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