# CVE-2019-3930: Memory corruption in Crestron AirMedia, Barco WePresent, Extron ShareLink, Teq AV IT WIPS710, SHARP PN-L703WA, Optoma WPS-Pro, Blackbox HD WPS, InFocus LiteShow3, and InFocus LiteShow4.

> Remote unauthenticated attackers can execute arbitrary code as root via a stack buffer overflow in the web interface of various wireless presentation devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xp69-2936-4v92

## What is CVE-2019-3930?

CVE-2019-3930 is a critical memory corruption vulnerability in Crestron AirMedia, Barco WePresent, Extron ShareLink, Teq AV IT WIPS710, SHARP PN-L703WA, Optoma WPS-Pro, Blackbox HD WPS, InFocus LiteShow3, and InFocus LiteShow4., published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 a stack buffer overflow in libAwgCgi.so's PARSERtoCHAR function. A remote, unauthenticated attacker can use this vulnerability to execute arbitrary code as root via a crafted request to the return.cgi endpoint.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2019-3930?

It affects 12 products.


Products: Barco Wepresent Wipg-1000p Firmware, Barco Wepresent Wipg-1600w Firmware, Blackbox Hd Wireless Presentation System Firmware, Crestron Am-100 Firmware, Crestron Am-101 Firmware, Extron Sharelink 200 Firmware, Extron Sharelink 250 Firmware, Infocus Liteshow3 Firmware, Infocus Liteshow4 Firmware, Optoma Wps-Pro Firmware, Sharp Pn-L703wa Firmware, Teqavit Wips710 Firmware.

## How do I fix CVE-2019-3930?

No fix has been published for CVE-2019-3930 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3930 being exploited?

There is no known exploitation of CVE-2019-3930 in the wild and no public exploit code.

## Other vulnerabilities in Crestron AirMedia, Barco WePresent, Extron ShareLink, Teq AV IT WIPS710, SHARP PN-L703WA, Optoma WPS-Pro, Blackbox HD WPS, InFocus LiteShow3, and InFocus LiteShow4.

- [CVE-2019-3929](https://insights.sbomify.com/CVE-2019-3929/): Crestron Multiple Products Command Injection (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3930 and fix it if it is affected.

What it is: CVE-2019-3930 is a critical memory corruption vulnerability in Crestron AirMedia, Barco WePresent, Extron ShareLink, Teq AV IT WIPS710, SHARP PN-L703WA, Optoma WPS-Pro, Blackbox HD WPS, InFocus LiteShow3, and InFocus LiteShow4., published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3930 in the wild and no public exploit code.

Affected product: Crestron AirMedia, Barco WePresent, Extron ShareLink, Teq AV IT WIPS710, SHARP PN-L703WA, Optoma WPS-Pro, Blackbox HD WPS, InFocus LiteShow3, and InFocus LiteShow4.. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-3930/ (Markdown: https://insights.sbomify.com/CVE-2019-3930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3930
- OSV: https://osv.dev/vulnerability/CVE-2019-3930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3930/
Summaries are generated and may contain mistakes; the official description above is the record.