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

> Remote attackers can bypass authentication and gain administrator access on Tenda A5s routers by manipulating the admin:language cookie.

- **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:** 22 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fm6q-42wm-2w9x

## What is CVE-2014-5246?

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

### Official description

The Shenzhen Tenda Technology Tenda A5s router with firmware 3.02.05_CN allows remote attackers to bypass authentication and gain administrator access by setting the admin:language cookie to zh-cn.

Weakness: CWE-264

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

It affects 2 products.


Products: Tenda A5s, Tenda A5s Firmware.

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

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

## Is CVE-2014-5246 being exploited?

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

Public exploit code:

- Tenda A5s Router 3.02.05_CN - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5246 is a critical authentication bypass vulnerability in n/a, published on 22 Aug 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-5246 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-5246/ (Markdown: https://insights.sbomify.com/CVE-2014-5246/index.md)
```

## Sources

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

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