CVE-2021-45556
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 · uneditedCertain NETGEAR devices are affected by command injection by an authenticated user. This affects GS108Tv2 before 5.4.2.36, GS110TPP before 7.0.7.2, GS110TPv2 before 5.4.2.36., GS110TPv3 before 7.0.7.2, GS308T before 1.0.3.2, GS310TP before 1.0.3.2, GS724TPP before 2.0.6.3, GS724TPv2 before 2.0.6.3, GS728TPPv2 before 6.0.8.2, GS728TPv2 before 6.0.8.2, GS752TPP before 6.0.8.2, GS752TPv2 before 6.0.8.2, MS510TXM before 1.0.4.2, and MS510TXUP before 1.0.4.2.
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 analysisUser input reaches a command interpreter without being fully separated from the command itself, so an attacker can append instructions of their own. Because those run with the application's privileges, it frequently means control of the host. The lasting fix is to avoid constructing commands from input — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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< 5.4.2.36< 7.0.7.2< 5.4.2.36< 1.0.3.2< 7.0.7.2< 1.0.3.2< 2.0.6.3< 2.0.6.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.0.3.22.0.6.35.4.2.36
Upgrade to the minimum fixed version for your model: GS108Tv2 to 5.4.2.36, GS110TPP to 7.0.7.2, GS110TPv2 to 5.4.2.36, GS110TPv3 to 7.0.7.2, GS308T to 1.0.3.2, GS310TP to 1.0.3.2, GS724TPP to 2.0.6.3, GS724TPv2 to 2.0.6.3
- 1. Identify the exact switch model (GS108Tv2, GS110TPP, GS110TPv2, GS110TPv3, GS308T, GS310TP, GS724TPP, or GS724TPv2)
- 2. Determine the current firmware version by logging into the switch web interface or checking via console
- 3. Download the appropriate fixed firmware version from the NETGEAR support website (support.netgear.com) for your specific model
- 4. Back up the current switch configuration through the web interface (System > Configuration File > Backup)
- 5. Access the switch web interface and navigate to the firmware upgrade section (Maintenance > Firmware Upgrade)
- 6. Upload and apply the new firmware file
- 7. After the switch reboots, verify the firmware version matches the fixed release (e.g., 5.4.2.36 for GS108Tv2)
- 8. Restore the configuration if needed and verify normal operation
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45556 — 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-2021-45556 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