CVE-2022-36779
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 · uneditedPROSCEND - PROSCEND / ADVICE .Ltd - G/5G Industrial Cellular Router (with GPS)4 Unauthenticated OS Command Injection Proscend M330-w / M33-W5 / M350-5G / M350-W5G / M350-6 / M350-W6 / M301-G / M301-GW ADVICE ICR 111WG / https://www.proscend.com/en/category/industrial-Cellular-Router/industrial-Cellular-Router.html https://cdn.shopify.com/s/files/1/0036/9413/3297/files/ADVICE_Industrial_4G_LTE_Cellular_Router_ICR111WG.pdf?v=1620814301
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 confidenceUnauthenticated OS command injection in PROSCEND and ADVICE industrial cellular routers (models M330-w through ICR 111WG) allows remote attackers to execute arbitrary operating system commands without any authentication, likely via insecure input handling in web management interfaces.
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.11< 1.11< 1.02< 1.02< 1.02< 1.02< 2.20< 2.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the router web interface or check physical device label to confirm the exact model (M330 W, M330 W5, M350 5g, M350 W5g, M350 6, M350 W6, M301 G, M301 Gw, or ICR 111WG)Affected if Model matches Proscend M330-w through ICR 111WG product line
-
Check installed firmware versionLog into the router web management interface and navigate to System Status or Firmware Info page to view the current firmware version. Compare against affected versions: M330 W/W5 < 1.11, M350 5g/W5g/6/W6 < 1.02, M301 G/Gw < 2.20Affected if Firmware version is lower than the affected version for your model
-
Verify web management interface accessibilityConfirm whether the router web management interface (HTTP/HTTPS on ports 80/443 or custom ports) is accessible from the network. Check router firewall settings and port forwarding rulesAffected if Web management interface is accessible from untrusted networks (internet or guest VLANs)
-
Check remote management settingsIn the router web interface, examine the Administration or Remote Access settings to determine if remote management via web interface is enabled and from which IP sourcesAffected if Remote web management is enabled and permits access from non-trusted IP addresses
Device is affected if it is a Proscend M330-w through ICR 111WG router running firmware below the specified version AND its web management interface is accessible from untrusted networks.
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.
dbcve · scoped1.021.112.20
Isolate affected routers behind firewalls with strict ACLs limiting management access to trusted IPs, apply vendor firmware updates when available, and disable unauthenticated management interfaces exposed to the internet.
Firmware 1.11 for M330-W/M330-W5; Firmware 1.02 for M350 series; Firmware 2.20 for M301-G/GW (or latest available from PROSCEND)
- 1. Identify the exact model number of the PROSCEND device (M330-W, M330-W5, M350-5G, M350-W5G, M350-6, M350-W6, M301-G, or M301-GW)
- 2. Check the current firmware version by accessing the device's web interface or administrative console
- 3. Navigate to the PROSCEND official support page or contact PROSCEND technical support to obtain the latest firmware
- 4. Download the firmware version 1.11 or later for M330-W/M330-W5 devices
- 5. Download the firmware version 1.02 or later for M350-5G/M350-W5G/M350-6/M350-W6 devices
- 6. Download the firmware version 2.20 or later for M301-G/M301-GW devices
- 7. Follow the manufacturer's firmware upgrade procedure, typically found in the device administration manual
- 8. After upgrading, verify the firmware version has been successfully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36779 — 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-2022-36779 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