# CVE-2025-35010: Microhard Bullet-LTE and IPn4Gii AT+MNPINGTM Argument Injection

> Attackers with local access can inject commands via the AT+MNPINGTM argument to escalate privileges in Microhard LTE devices.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2025
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-pj5v-grmp-4755

## What is CVE-2025-35010?

CVE-2025-35010 is a high-severity command injection vulnerability in Microhard IPn4Gii / Bullet-LTE Firmware, published on 8 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Products that incorporate the Microhard BulletLTE-NA2 and IPn4Gii-NA2 are vulnerable to a post-authentication command injection issue in the AT+MNPINGTM command that can lead to privilege escalation. This is an instance of CWE-88, "Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')," and is estimated as a CVSS 7.1 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). This issue has not been generally fixed at the time of this CVE record's first publishing.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2025-35010?

It affects 2 products.


Products: Microhardcorp Bulletlte-Na2 Firmware, Microhardcorp Ipn4gii-Na2 Firmware.

## How do I fix CVE-2025-35010?

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

## Is CVE-2025-35010 being exploited?

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

## Other vulnerabilities in Microhard IPn4Gii / Bullet-LTE Firmware

- [CVE-2025-35004](https://insights.sbomify.com/CVE-2025-35004/): Microhard Bullet-LTE and IPn4Gii AT+MFIP Argument Injection (high 7.1)
- [CVE-2025-35005](https://insights.sbomify.com/CVE-2025-35005/): Microhard Bullet-LTE and IPn4Gii AT+MFMAC Argument Injection (high 7.1)
- [CVE-2025-35006](https://insights.sbomify.com/CVE-2025-35006/): Microhard Bullet-LTE and IPn4Gii AT+MFPORTFWD Argument Injection (high 7.1)
- [CVE-2025-35007](https://insights.sbomify.com/CVE-2025-35007/): Microhard Bullet-LTE and IPn4Gii AT+MFRULE Argument Injection (high 7.1)
- [CVE-2025-35008](https://insights.sbomify.com/CVE-2025-35008/): Microhard Bullet-LTE and IPn4Gii AT+MMNAME Argument Injection (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-35010 and fix it if it is affected.

What it is: CVE-2025-35010 is a high-severity command injection vulnerability in Microhard IPn4Gii / Bullet-LTE Firmware, published on 8 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-35010 exists.

Affected product: Microhard IPn4Gii / Bullet-LTE Firmware. 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-2025-35010/ (Markdown: https://insights.sbomify.com/CVE-2025-35010/index.md)
```

## Sources

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

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