CVE-2014-1982
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 · uneditedThe administrative interface in Allied Telesis AT-RG634A ADSL Broadband router 3.3+, iMG624A firmware 3.5, iMG616LH firmware 2.4, and iMG646BD firmware 3.5 allows remote attackers to gain privileges and execute arbitrary commands via a direct request to cli.html.
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 confidenceThe administrative web interface in Allied Telesis AT-RG634A and related broadband router models (iMG624A, iMG616LH, iMG646BD) contains a command injection vulnerability where a direct unauthenticated request to cli.html allows remote attackers to execute arbitrary commands with administrative 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= 3.5all versions= 3.3\+all versions= 3.5all versions= \+2.4all versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 modelAccess the router web interface or check the device label/management console to determine if the model is AT-RG634A, iMG624A, iMG616LH, or iMG646BDAffected if The device is any of these four models listed in the affected products
-
Check the installed firmware versionLog into the router administrative interface and navigate to the status or system information page to view the firmware version; alternatively, check via CLI if accessibleAffected if Firmware version matches or exceeds 3.3 for AT-RG634A, 3.5 for iMG624A/iMG646BD, or 2.4 for iMG616LH (or if the device is running any firmware version at all, since all versions are affected)
-
Verify if the web administrative interface is network-accessibleAttempt to access the router IP address on ports 80 (HTTP) or 443 (HTTPS) from an external network or untrusted segment; check router firewall/access control settings to determine if remote web management is enabledAffected if The web interface (cli.html) is reachable from untrusted network segments or the internet
-
Confirm cli.html endpoint is exposedSend an HTTP GET or POST request directly to http://[router-ip]/cli.html and verify the endpoint responds; no authentication should be required for the vulnerability to existAffected if The cli.html endpoint returns a valid HTTP response without requiring authentication
If the device is an Allied Telesis AT-RG634A, iMG624A, iMG616LH, or iMG646BD router and its web administrative interface is accessible from untrusted networks, the environment is affected by this vulnerability.
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 if available; otherwise, disable remote administrative access to the web interface and restrict management to trusted internal networks only, or implement firewall rules to block external access to port 80/443 on affected devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1982 — 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-2014-1982 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