CVE-2025-2957
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 · uneditedA vulnerability was found in TRENDnet TEW-411BRP+ 2.07. It has been classified as problematic. Affected is the function sub_401DB0 of the file /usr/sbin/httpd of the component HTTP Request Handler. The manipulation leads to null pointer dereference. The attack can only be initiated within the local network. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 the HTTP request handler (function sub_401DB0 in /usr/sbin/httpd) of TRENDnet TEW-411BRP+ router firmware 2.07. The vulnerability can be exploited via specially crafted HTTP requests sent from within the local network, causing the HTTP daemon to crash or experience undefined behavior.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 device modelLog into the router admin interface or check the device label to confirm the model is TRENDnet TEW-411BRP+Affected if The device is not a TRENDnet TEW-411BRP+ router
-
Check firmware versionAccess the router's web admin interface (typically at 192.168.1.1) and navigate to the Status or System section to view the firmware version, or use the router's firmware version check command if accessible via CLIAffected if Firmware version is 2.07 exactly (the only version listed as affected)
-
Verify HTTP service is runningFrom within the local network, attempt to access the router's HTTP interface via a web browser at http://192.168.1.1 or the configured router IP addressAffected if The HTTP service responds to requests, indicating the vulnerable /usr/sbin/httpd daemon is running
-
Confirm HTTP handler vulnerabilitySend a specially crafted HTTP request to the router's HTTP interface. The vulnerability exists in function sub_401DB0 of the HTTP request handler. While exact request details are not provided, the vulnerability triggers from the local network against the request processing routineAffected if The HTTP daemon crashes, becomes unresponsive, or exhibits undefined behavior in response to the crafted request
A user is affected if they own a TRENDnet TEW-411BRP+ router running firmware version 2.07 and the HTTP service is accessible from their local network, as the null pointer dereference in the HTTP request handler will cause a crash or undefined behavior when triggered by a specially crafted HTTP request.
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 dataNetwork access to the router's HTTP interface should be restricted to trusted internal hosts only. Given the vendor's non-response and end-of-life status, consider replacing the device with a currently supported model.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2957 — 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-2025-2957 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