dbcve.org
Tl Wr902ac FirmwareOperating system · Tp Link

CVE-2023-50225

MEDIUM · 6.8 CVSS v3.0 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Zero-click

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 · unedited
TP-Link TL-WR902AC dm_fillObjByStr Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of TP-Link TL-WR902AC routers. Authentication is required to exploit this vulnerability. The specific flaw exists within the libcmm.so module. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. . Was ZDI-CAN-21819.

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 confidence

A stack-based buffer overflow vulnerability exists in the dm_fillObjByStr function within the libcmm.so module of TP-Link TL-WR902AC routers. The flaw results from insufficient length validation before copying user-supplied data into a fixed-size stack buffer, allowing authenticated attackers to overflow the buffer and execute arbitrary code with root privileges.

MitigationApply vendor firmware updates when available; until then, restrict administrative access to trusted networks only, disable remote management interfaces, and enforce strong authentication credentials.

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
Tl Wr902ac FirmwareOperating system
Affected:= 0.9.1_0.3_v008a.0

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router web interface or check the device label to confirm the model is TP-Link TL-WR902AC
    Affected if Device is not a TP-Link TL-WR902AC router - this vulnerability only affects that specific model
  2. Check installed firmware version
    Log into the router administration panel, typically at 192.168.0.1 or 192.168.1.1, and navigate to System Tools > Firmware Upgrade or Status page to view the installed firmware version
    Affected if Firmware version is exactly 0.9.1_0.3_v008a.0 - this is the only confirmed affected version
  3. Verify libcmm.so module presence
    Access router via SSH or telnet if enabled, then search for the libcmm.so file, typically found in /lib or /usr/lib directories
    Affected if The libcmm.so library file exists on the device - the vulnerable dm_fillObjByStr function resides in this module
  4. Check administrative access exposure
    Examine router firewall settings and WAN access configuration to determine if the admin interface is accessible from external networks
    Affected if Remote management/admin interface is exposed to WAN or untrusted networks - this enables remote authenticated attackers to reach the vulnerable function
  5. Verify authentication configuration
    Check router security settings to confirm whether strong admin passwords are enforced and if default credentials remain in use
    Affected if Weak or default administrator credentials are in use - attackers need valid authentication to trigger the buffer overflow in dm_fillObjByStr

A user is affected only if they have a TP-Link TL-WR902AC router running firmware version 0.9.1_0.3_v008a.0 with the libcmm.so module present and the administrative interface exposed to untrusted networks with weak credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available; until then, restrict administrative access to trusted networks only, disable remote management interfaces, and enforce strong authentication credentials.

Fix this in Tl Wr902ac Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50225 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50225 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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