# CVE-2017-15329: SQL injection in UMA

> An authenticated attacker can execute arbitrary SQL queries via crafted HTTP requests in the Huawei UMA operation and maintenance module due to insufficient input validation.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hp7m-r9j9-3vm5

## What is CVE-2017-15329?

CVE-2017-15329 is a high-severity SQL injection vulnerability in Huawei Technologies Co., Ltd. UMA, published on 15 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Huawei UMA V200R001C00 has a SQL injection vulnerability in the operation and maintenance module. An attacker logs in to the system as a common user and sends crafted HTTP requests that contain malicious SQL statements to the affected system. Due to a lack of input validation on HTTP requests that contain user-supplied input, successful exploitation may allow the attacker to execute arbitrary SQL queries.

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

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

It affects 1 product.


Products: Huawei Uma Firmware.

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

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

## Is CVE-2017-15329 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15329 is a high-severity SQL injection vulnerability in Huawei Technologies Co., Ltd. UMA, published on 15 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15329 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. UMA. 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-15329/ (Markdown: https://insights.sbomify.com/CVE-2017-15329/index.md)
```

## Sources

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

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