CVE-2021-33514
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 unauthenticated attacker via the vulnerable /sqfs/lib/libsal.so.0.0 library used by a CGI application, as demonstrated by setup.cgi?token=';$HTTP_USER_AGENT;' with an OS command in the User-Agent field. This affects GC108P before 1.0.7.3, GC108PP before 1.0.7.3, GS108Tv3 before 7.0.6.3, GS110TPPv1 before 7.0.6.3, GS110TPv3 before 7.0.6.3, GS110TUPv1 before 1.0.4.3, GS710TUPv1 before 1.0.4.3, GS716TP before 1.0.2.3, GS716TPP before 1.0.2.3, GS724TPPv1 before 2.0.4.3, GS724TPv2 before 2.0.4.3, GS728TPPv2 before 6.0.6.3, GS728TPv2 before 6.0.6.3, GS752TPPv1 before 6.0.6.3, GS752TPv2 before 6.0.6.3, MS510TXM before 1.0.2.3, and MS510TXUP before 1.0.2.3.
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 shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the os 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< 1.0.7.3< 1.0.7.3< 7.0.6.3< 7.0.6.3< 7.0.6.3< 1.0.4.3< 1.0.4.3< 1.0.2.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
- 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
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.2.31.0.4.31.0.7.3
Firmware version 1.0.7.3 for GC108P/GC108PP; 7.0.6.3 for GS108Tv3/GS110TPPv1/GS110TPv3; 1.0.4.3 for GS110TUPv1/GS710TUPv1; 1.0.2.3 for GS716TP/GS716TPP/MS510TXM/MS510TXUP; 2.0.4.3 for GS724TPPv1/GS724TPv2; 6.0.6.3 for GS728TPPv2/GS752TPPv1/GS752TPv2 (or later stable releases)
- 1. Identify the specific NETGEAR switch model from the affected list (GC108P, GC108PP, GS108Tv3, GS110TPPv1, GS110TPv3, GS110TUPv1, GS710TUPv1, GS716TP, GS716TPP, GS724TPPv1, GS724TPv2, GS728TPPv2, GS728TPv2, GS752TPPv1, GS752TPv2, MS510TXM, or MS510TXUP)
- 2. Visit the NETGEAR support website at https://www.netgear.com/support/
- 3. Enter the specific model number in the search or support lookup
- 4. Navigate to the Downloads/Firmware section for the device
- 5. Download the latest firmware version that is at or above the fixed version for your model: GC108P/GC108PP need 1.0.7.3+, GS108Tv3/GS110TPPv1/GS110TPv3 need 7.0.6.3+, GS110TUPv1/GS710TUPv1 need 1.0.4.3+, GS716TP/GS716TPP need 1.0.2.3+, GS724TPPv1/GS724TPv2 need 2.0.4.3+, GS728TPPv2/GS752TPPv1/GS752TPv2 need 6.0.6.3+, MS510TXM/MS510TXUP need 1.0.2.3+
- 6. Access the device web management interface
- 7. Go to the Firmware Update or Administration section
- 8. Upload and apply the new firmware file
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-33514 — 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-33514 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