# CVE-2014-1982: Auth bypass in n/a

> Remote attackers can bypass authentication and execute arbitrary commands on Allied Telesis routers by accessing a specific administrative interface page.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xp8f-6f2w-prw8

## What is CVE-2014-1982?

CVE-2014-1982 is a critical authentication bypass vulnerability in n/a, published on 28 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2014-1982?

It affects 8 products.


Products: Alliedtelesis At-Rg634a, Alliedtelesis At-Rg634a Firmware, Alliedtelesis Img616lh, Alliedtelesis Img616lh Firmware, Alliedtelesis Img624a, Alliedtelesis Img624a Firmware, Alliedtelesis Img646bd, Alliedtelesis Img646bd Firmware.

## How do I fix CVE-2014-1982?

No fix has been published for CVE-2014-1982 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-1982 being exploited?

There is no known exploitation of CVE-2014-1982 in the wild and no public exploit code.

Public exploit code:

- Allied Telesis AT-RG634A ADSL Broadband Router - Web Shell (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1982 and fix it if it is affected.

What it is: CVE-2014-1982 is a critical authentication bypass vulnerability in n/a, published on 28 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-1982 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-1982/ (Markdown: https://insights.sbomify.com/CVE-2014-1982/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-1982
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-1982
- OSV: https://osv.dev/vulnerability/CVE-2014-1982

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-1982/
Summaries are generated and may contain mistakes; the official description above is the record.