CVE-2021-28844
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 · uneditedNull Pointer Dereference vulnerability exists in TRENDnet TEW-755AP 1.11B03, TEW-755AP2KAC 1.11B03, TEW-821DAP2KAC 1.11B03, and TEW-825DAP 1.11B03 by sending the POST request to apply_cgi via a do_graph_auth action without a session_id key.
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 confidenceA null pointer dereference vulnerability exists in multiple TRENDnet wireless access point firmware versions (1.11B03). The vulnerability is triggered by sending a POST request to the apply_cgi endpoint with the do_graph_auth action while omitting the session_id parameter, causing the application to dereference a null pointer.
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.11b03= 1.11b03= 1.11b03= 1.11b03CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 TRENDnet access point modelCheck the device label, web management interface, or DHCP lease information to determine the exact model (Tew 755ap, Tew 755ap2kac, Tew 821dap2kac, or Tew 825dap)Affected if The device is not one of the four listed models (Tew 755ap, Tew 755ap2kac, Tew 821dap2kac, Tew 825dap)
-
Check the installed firmware versionLog into the device web management interface and navigate to the Status or System Information page to view the firmware version, or use SNMP/CLI if availableAffected if The firmware version is exactly 1.11b03 (note: only this specific version is affected)
-
Verify the apply_cgi endpoint is accessibleAttempt to access the apply_cgi endpoint via HTTP/HTTPS on the device (typically at /apply_cgi or similar path used by TRENDnet web interface)Affected if The apply_cgi endpoint is reachable and responds to requests
-
Confirm web management interface is enabledCheck the device configuration to verify the HTTP/HTTPS management interface is enabled and accessible from the network segment being assessedAffected if The web-based management interface is enabled and accessible (this is required for the vulnerable endpoint to be exploitable)
You are affected if you are running exactly firmware version 1.11b03 on a Tew 755ap, Tew 755ap2kac, Tew 821dap2kac, or Tew 825dap device AND the web management interface with apply_cgi endpoint is accessible on your network.
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 vendor firmware updates when available. Until then, restrict network access to the device's management interface and consider placing affected devices behind a properly configured firewall to reduce exposure.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28844 — 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-28844 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