# CVE-2014-5071: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the checkPassword function in Symmetricom s350i devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 8 Jan 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9jfm-99hc-m6hx

## What is CVE-2014-5071?

CVE-2014-5071 is a critical SQL injection vulnerability in n/a, published on 8 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the checkPassword function in Symmetricom s350i 2.70.15 allows remote attackers to execute arbitrary SQL commands via vectors involving a username.

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

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

It affects 1 product.


Products: Microsemi S350i Firmware.

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

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

## Is CVE-2014-5071 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5070](https://insights.sbomify.com/CVE-2014-5070/): Privilege escalation in n/a (high 8.8)
- [CVE-2014-5068](https://insights.sbomify.com/CVE-2014-5068/): Path traversal in n/a (high 7.5)
- [CVE-2014-5069](https://insights.sbomify.com/CVE-2014-5069/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5071 is a critical SQL injection vulnerability in n/a, published on 8 Jan 2018. 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-5071 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-5071/ (Markdown: https://insights.sbomify.com/CVE-2014-5071/index.md)
```

## Sources

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

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