CVE-2022-40619
What it is
FunJSQ, a third-party module integrated on some NETGEAR routers and Orbi WiFi Systems, exposes an HTTP server over the LAN interface of affected devices. This interface is vulnerable to unauthenticated arbitrary command injection through the funjsq_access_token parameter. This affects R6230 before 1.1.0.112, R6260 before 1.1.0.88, R7000 before 1.0.11.134, R8900 before 1.0.5.42, R9000 before 1.0.5.42, and XR300 before 1.0.3.72 and Orbi RBR20 before 2.7.2.26, RBR50 before 2.7.4.26, RBS20 before 2.7.2.26, and RBS50 before 2.7.4.26.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering.
- Exploit odds
- 2.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.5% in the next 30 days (EPSS).
- Severity: 7.7 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.5% · EPSS, next 30 days
- Weakness
- CWE-77 · Command injection
- Record status
- Analyzed
Affected
- Netgear rbr20 Firmware < 2.7.2.26
- Netgear r6230 Firmware < 1.1.0.112
- Netgear r6260 Firmware < 1.1.0.88
- Netgear r7000 Firmware < 1.0.11.134
- Netgear r8900 Firmware < 1.0.5.42
- Netgear r9000 Firmware < 1.0.5.42
- Netgear rax120 Firmware < 1.2.8.40
- Netgear rax120v2 Firmware < 1.2.8.40
Attack profile CVSS 3.1 · 7.7
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-40619.md and follow it. Check whether this project is affected by CVE-2022-40619. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
