CVE-2021-35402
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 · uneditedPROLiNK PRC2402M 20190909 before 2021-06-13 allows live_api.cgi?page=satellite_list OS command injection via shell metacharacters in the ip parameter (for satellite_status).
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 · high confidenceThe PROLiNK PRC2402M router firmware before 2021-06-13 contains an unauthenticated OS command injection vulnerability in the live_api.cgi script. The satellite_list page accepts an 'ip' parameter that is passed to a system shell without sanitization, allowing attackers to inject arbitrary shell commands via shell metacharacters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 the device modelAccess the router web interface or check the device label/marketing materials to confirm the model is PROLiNK PRC2402MAffected if The device is a PROLiNK PRC2402M router
-
Check the firmware versionLog into the router web interface and navigate to the firmware/version information page, or use the router's administration CLI if available, to determine the installed firmware build dateAffected if The firmware build date is before 2021-06-13 or the version cannot be determined to be updated
-
Verify the vulnerable CGI script existsAttempt to access the live_api.cgi script on the router (e.g., http://[router-ip]/cgi-bin/live_api.cgi) via HTTP request and check for a responseAffected if The script responds and accepts parameters without authentication (indicating the vulnerable code path is present)
-
Assess network exposure of management interfaceDetermine if the router's web management interface (port 80/443) is accessible from untrusted networks such as the internet or guest networksAffected if The management interface is exposed to untrusted networks, allowing unauthenticated attackers to reach the vulnerable endpoint
The device is affected if it is a PROLiNK PRC2402M with firmware dated before 2021-06-13, and the router management interface is reachable by potential attackers.
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.
From vendor dataApply the vendor firmware update (2021-06-13 or later). If no update is available, restrict network access to the device's management interface and disable remote administration features as a temporary measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35402 — 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-35402 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