# CVE-2017-15322: Denial of service in Baggio-L03A

> An attacker can cause a service crash on specific Huawei smartphones by sending specially crafted NFC messages due to insufficient input validation.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xmqh-xx76-mgpj

## What is CVE-2017-15322?

CVE-2017-15322 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. Baggio-L03A, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Some Huawei smartphones with software of BGO-L03C158B003CUSTC158D001 and BGO-L03C331B009CUSTC331D001 have a DoS vulnerability due to insufficient input validation. An attacker could exploit this vulnerability by sending specially crafted NFC messages to the target device. Successful exploit could make a service crash.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Huawei Baggio-L03a Firmware.

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

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

## Is CVE-2017-15322 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15322 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. Baggio-L03A, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15322 in the wild and no public exploit code.

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

## Sources

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

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