# CVE-2019-14951: Security feature bypass in n/a

> Attackers can bypass brute-force protections to gain unauthorized access to vehicle multimedia screens via the mobile app's authentication process.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hhwc-fxxw-wfmx

## What is CVE-2019-14951?

CVE-2019-14951 is a high-severity vulnerability in n/a, published on 12 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Telenav Scout GPS Link app 1.x for iOS, as used with Toyota and Lexus vehicles, has an incorrect protection mechanism against brute-force attacks on the authentication process, which makes it easier for attackers to obtain multimedia-screen access via port 7050 on the cellular network, as demonstrated by a DrivingRestriction method call to uma/jsonrpc/mobile.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2019-14951?

It affects 1 product.


Products: Telenav Scout Gps Link.

## How do I fix CVE-2019-14951?

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

## Is CVE-2019-14951 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14951 and fix it if it is affected.

What it is: CVE-2019-14951 is a high-severity vulnerability in n/a, published on 12 Aug 2019. 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-2019-14951 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-2019-14951/ (Markdown: https://insights.sbomify.com/CVE-2019-14951/index.md)
```

## Sources

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

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