CVE-2022-40109
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 · uneditedTOTOLINK A3002R TOTOLINK-A3002R-He-V1.1.1-B20200824.0128 is vulnerable to Insecure Permissions via binary /bin/boa.
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 · moderate confidenceThe TOTOLINK A3002R router firmware (V1.1.1-B20200824.0128) contains the web server binary /bin/boa with insecure file permissions. This typically means the binary is either world-writable, has excessive permissions, or is owned by a non-privileged user, allowing attackers to modify or replace the binary to execute arbitrary code with elevated privileges.
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= 1.1.1-b20200824.0128CVSS 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 firmware versionAccess the router admin interface or extract firmware and check the version string. Look for version identifier '1.1.1-b20200824.0128' or check /etc/version, /etc/firmware_info, or similar version file in the firmware filesystem.Affected if Firmware version is exactly 1.1.1-b20200824.0128
-
Verify /bin/boa file ownershipIn the firmware filesystem or via router shell, run 'ls -la /bin/boa' to check the owner and group of the boa binary.Affected if The binary is NOT owned by root (or another privileged system user/group)
-
Check /bin/boa permissions for world-writabilityIn the firmware filesystem or via router shell, run 'ls -la /bin/boa' and examine the permission bits. Specifically check if the 'other' (last three bits) include 'w' (write permission).Affected if The binary has world-writable permissions (permission string shows 'w' in the last three bits, e.g., 777 or similar)
-
Verify /bin/boa has overly permissive modeCompare the actual permission bits to the expected secure mode of 755 (rwxr-xr-x) or stricter. Run 'stat /bin/boa' or 'ls -la /bin/boa' and interpret the octal permissions.Affected if Permissions are more permissive than 755 (e.g., 775, 777, or any mode granting write to group or others)
A defender is affected if running firmware version 1.1.1-b20200824.0128 AND the /bin/boa binary is either not root-owned or has permissions more permissive than 755 (especially world-writable).
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 dataReplace the binary with a properly permissioned version (owned by root, permissions 755 or stricter) or apply vendor firmware update that corrects the permission configuration.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40109 — 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-40109 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