# CVE-2017-6054: Hardcoded credentials in Hyundai Motor America Blue Link

> Attackers can decrypt sensitive user information using a hard-coded key in the Hyundai Blue Link mobile application.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 26 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fmxw-52w5-jc84

## What is CVE-2017-6054?

CVE-2017-6054 is a high-severity vulnerability in Hyundai Motor America Blue Link, published on 26 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use of Hard-Coded Cryptographic Key issue was discovered in Hyundai Motor America Blue Link 3.9.5 and 3.9.4. The application uses a hard-coded decryption password to protect sensitive user information.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 1 product.


Products: Hyundai Blue Link.

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

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

## Is CVE-2017-6054 being exploited?

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

## Other vulnerabilities in Hyundai Motor America Blue Link

- [CVE-2017-6052](https://insights.sbomify.com/CVE-2017-6052/): Other in Hyundai Motor America Blue Link (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6054 is a high-severity vulnerability in Hyundai Motor America Blue Link, published on 26 Apr 2017. 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-6054 in the wild and no public exploit code.

Affected product: Hyundai Motor America Blue Link. 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-6054/ (Markdown: https://insights.sbomify.com/CVE-2017-6054/index.md)
```

## Sources

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

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