# CVE-2017-3217: Missing authorization in LMU 3030 OBD-II

> Attackers can send administrative commands to CalAmp OBD-II devices if the SMS interface lacks a password, allowing full device control.

- **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:** 24 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gj9r-4hg5-ccw4

## What is CVE-2017-3217?

CVE-2017-3217 is a high-severity missing authorization vulnerability in CalAmp LMU 3030 OBD-II, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CalAmp LMU 3030 series OBD-II CDMA and GSM devices has an SMS (text message) interface that can be deployed where no password is configured for this interface by the integrator / reseller. This interface must be password protected, otherwise, the attacker only needs to know the phone number of the device (via an IMSI Catcher, for example) to send administrative commands to the device. These commands can be used to provide ongoing, real-time access to the device and can configure parameters such as IP addresses, firewall rules, and passwords.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 3 products.


Products: Calamp Lmu 3030 Cdma Firmware, Calamp Lmu 3030 Gsm Firmware, Calamp Lmu 3030 Obd-Ii Firmware.

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

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

## Is CVE-2017-3217 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3217 is a high-severity missing authorization vulnerability in CalAmp LMU 3030 OBD-II, published on 24 Jul 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-2017-3217 in the wild and no public exploit code.

Affected product: CalAmp LMU 3030 OBD-II. 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-3217/ (Markdown: https://insights.sbomify.com/CVE-2017-3217/index.md)
```

## Sources

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

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