CVE-2019-13149
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 · uneditedAn issue was discovered in TRENDnet TEW-827DRU firmware before 2.05B11. There is a command injection in apply.cgi (exploitable with authentication) via the key passwd in Routing RIP Settings.
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 confidenceAuthenticated command injection vulnerability in TRENDnet TEW-827DRU routers allows remote attackers to execute arbitrary OS commands via the 'passwd' parameter in apply.cgi when configuring RIP routing settings. The vulnerability exists in firmware versions prior to 2.05B11.
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< 2.05b11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Identify the device modelCheck the router label or access the web admin interface and look for the model number displayed on the login page or in the status/dashboard section. Confirm it is a TRENDnet TEW-827DRU.Affected if The device is a TRENDnet TEW-827DRU router.
-
Check the installed firmware versionLog into the router web admin interface, navigate to Status or System section, and locate the firmware version field. Alternatively, check the download/release notes page on TRENDnet's support site for version 2.05B11 and compare.Affected if The firmware version is displayed as lower than 2.05B11 (for example, 2.05B10, 2.05B09, or earlier).
-
Verify if RIP routing is enabledIn the router web admin interface, navigate to the Routing or RIP settings section (often under Advanced or Network Settings). Check whether RIP (Routing Information Protocol) is configured or enabled.Affected if RIP is enabled or configured on the device, making the apply.cgi with the vulnerable 'passwd' parameter accessible.
-
Confirm administrative interface accessibilityDetermine if the router web admin interface (typically on ports 80 or 443) is reachable from untrusted networks. Check firewall rules, port forwarding settings, or VPN access controls that govern who can reach the admin login page.Affected if The administrative interface is accessible from networks outside the trusted administrative perimeter.
The device is affected if it is a TRENDnet TEW-827DRU running firmware version lower than 2.05B11 and the router admin interface is accessible, regardless of whether RIP is explicitly enabled since the apply.cgi endpoint exists in the firmware build.
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 data2.05b11
Upgrade firmware to version 2.05B11 or later. Until patched, limit administrative interface access to trusted IPs and ensure strong credentials to reduce attack surface.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13149 — 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-2019-13149 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