# CVE-2017-8835: SQL injection in n/a

> SQL injection in Peplink Balance routers allows attackers to enumerate user accounts via the bauth cookie, requiring a firmware upgrade to fix.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cwh4-2qh3-3jxc

## What is CVE-2017-8835?

CVE-2017-8835 is a critical SQL injection vulnerability in n/a, published on 5 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before fw-b305hw2_380hw6_580hw2_710hw3_1350hw2_2500-7.0.1-build2093. An attack vector is the bauth cookie to cgi-bin/MANGA/admin.cgi. One impact is enumeration of user accounts by observing whether a session ID can be retrieved from the sessions database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-8835?

It affects 6 products.


Products: Peplink 1350hw2 Firmware, Peplink 2500 Firmware, Peplink 380hw6 Firmware, Peplink 580hw2 Firmware, Peplink 710hw3 Firmware, Peplink B305hw2 Firmware.

## How do I fix CVE-2017-8835?

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

## Is CVE-2017-8835 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8835 exists.

Public exploit code:

- Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure (exploitdb)
- Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure (exploitdb)
- Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure (exploitdb)
- Peplink Balance routers SQLi (metasploit)

## Other vulnerabilities in n/a

- [CVE-2017-8837](https://insights.sbomify.com/CVE-2017-8837/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8836](https://insights.sbomify.com/CVE-2017-8836/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-8841](https://insights.sbomify.com/CVE-2017-8841/): Path traversal in n/a (high 8.1)
- [CVE-2017-8838](https://insights.sbomify.com/CVE-2017-8838/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-8839](https://insights.sbomify.com/CVE-2017-8839/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8835 and fix it if it is affected.

What it is: CVE-2017-8835 is a critical SQL injection vulnerability in n/a, published on 5 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8835 exists.

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-2017-8835/ (Markdown: https://insights.sbomify.com/CVE-2017-8835/index.md)
```

## Sources

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

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