CVE-2022-37842
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 · uneditedIn TOTOLINK A860R V4.1.2cu.5182_B20201027, the parameters in infostat.cgi are not filtered, causing a buffer overflow vulnerability.
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 confidenceA buffer overflow vulnerability exists in the infostat.cgi component of TOTOLINK A860R router firmware V4.1.2cu.5182_B20201027. The vulnerability stems from insufficient input validation on parameters passed to the CGI script, allowing an attacker to overflow a buffer and potentially execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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= 4.1.2cu.5182_b20201027CVSS 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
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.
-
Check router firmware versionAccess the router's web management interface and navigate to System Status or Firmware Version page. Alternatively, check the firmware file name or checksum if you have access to the device via SSH/TFTP.Affected if The firmware version displayed is exactly 4.1.2cu.5182_b20201027.
-
Verify infostat.cgi component existsAttempt to access the CGI script via HTTP/HTTPS request to: http://<router-ip>/cgi-bin/infostat.cgiAffected if The script responds (even with an error) indicating it exists on the device.
-
Confirm web management interface is enabledCheck if the router's HTTP/HTTPS management interface is accessible from the network. This can be done by attempting to access the router's IP address on ports 80 or 443.Affected if The web interface responds and accepts connections, meaning the vulnerable CGI script is reachable over the network.
-
Determine if remote administration is enabledCheck the router's admin settings for remote access configuration. Look for options like 'Remote Management', 'Remote Access', or 'Web Access from WAN' in the administration settings.Affected if Remote administration is enabled, allowing the vulnerable CGI to be accessed from external networks.
You are affected if your TOTOLINK A860R firmware is exactly version 4.1.2cu.5182_b20201027 AND the infostat.cgi script is accessible through the router's web interface.
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 dataUpgrade to a patched firmware version if available. If no update exists, restrict network access to the router's web management interface and disable remote administration to reduce attack surface.
- Consultation6.0 h
- Implementation30.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37842 — 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-2022-37842 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