Certain NETGEAR devices are affected by command injection by an authenticated user.
Certain NETGEAR devices are affected by command injection by an authenticated user. This affects RBK852 before 3.2.17.12, RBK853 before 3.2.17.12, RBK854 before 3.2.17.12, RBR850 before 3.2.17.12, and RBS850 before 3.2.17.12.
- Published
- Mar 23, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 45th percentile
- CWE
- CWE-77
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 8.4
- CNA · mitre
- 8.4
- agree
CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:H/S:C/UI:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| netgear | rbk852 firmware | cpe:2.3:o:netgear:rbk852_firmware |
| netgear | rbk852 | cpe:2.3:h:netgear:rbk852 |
| netgear | rbk853 firmware | cpe:2.3:o:netgear:rbk853_firmware |
| netgear | rbk853 | cpe:2.3:h:netgear:rbk853 |
| netgear | rbk854 firmware | cpe:2.3:o:netgear:rbk854_firmware |
| netgear | rbk854 | cpe:2.3:h:netgear:rbk854 |
| netgear | rbr850 firmware | cpe:2.3:o:netgear:rbr850_firmware |
| netgear | rbr850 | cpe:2.3:h:netgear:rbr850 |
| netgear | rbs850 firmware | cpe:2.3:o:netgear:rbs850_firmware |
| netgear | rbs850 | cpe:2.3:h:netgear:rbs850 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear rbk852 firmwarebefore 3.2.17.12
- netgear rbk853 firmwarebefore 3.2.17.12
- netgear rbk854 firmwarebefore 3.2.17.12
- netgear rbr850 firmwarebefore 3.2.17.12
- netgear rbs850 firmwarebefore 3.2.17.12
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-38513Certain NETGEAR devices are affected by authentication bypass.40Plan
- CVE-2021-29079Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.38Monitor
- CVE-2021-29078Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.38Monitor
- CVE-2021-29076Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.38Monitor
- CVE-2021-29066Certain NETGEAR devices are affected by authentication bypass.38Monitor
- CVE-2021-29071Certain NETGEAR devices are affected by command injection by an authenticated user.36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2021-38513140 days apartCertain NETGEAR devices are affected by authentication bypass.40Plan
- CVE-2021-290660 days apartCertain NETGEAR devices are affected by authentication bypass.38Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.