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

> Unauthenticated attackers can perform SQL injection via the ONVIF device service to read admin credentials and compromise the device.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 26 Sep 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jm85-849j-wmxc

## What is CVE-2017-14743?

CVE-2017-14743 is a high-severity SQL injection vulnerability in n/a, published on 26 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Faleemi FSC-880 00.01.01.0048P2 devices allow unauthenticated SQL injection via the Username element in an XML document to /onvif/device_service, as demonstrated by reading the admin password.

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

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

It affects 1 product.


Products: Faleemi Fsc-880 Firmware.

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

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

## Is CVE-2017-14743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14743 is a high-severity SQL injection vulnerability in n/a, published on 26 Sep 2017. 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-2017-14743 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-2017-14743/ (Markdown: https://insights.sbomify.com/CVE-2017-14743/index.md)
```

## Sources

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

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