# CVE-2014-8331: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to modify configuration settings or use device functions on Huawei HiLink routers.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pxrg-788p-rrf9

## What is CVE-2014-8331?

CVE-2014-8331 is a medium-severity vulnerability in n/a, published on 20 Oct 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3236 before E3276sTCPU-V200R002B470D13SP00C00 and E3276sWebUI-V100R007B100D03SP01C03 and E3276 before E3236sTCPU-V200R002B146D41SP00C00 and E3236sWebUI-V100R007B100D03SP01C03 allow remote attackers to hijack the authentication of administrators for requests that (1) change configuration settings or (2) use device functions.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 2 products.


Products: Huawei E3236 Firmware, Huawei E3276 Firmware.

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

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

## Is CVE-2014-8331 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5395](https://insights.sbomify.com/CVE-2014-5395/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8331 is a medium-severity vulnerability in n/a, published on 20 Oct 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-8331 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-8331/ (Markdown: https://insights.sbomify.com/CVE-2014-8331/index.md)
```

## Sources

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

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