# CVE-2023-40291: Hardcoded credentials in n/a

> Attackers can gain root access to Harman Infotainment systems via SSH using a hardcoded internal project name as the password.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 14 Aug 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-2mw3-4c3p-vv6p

## What is CVE-2023-40291?

CVE-2023-40291 is a medium-severity vulnerability in n/a, published on 14 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Harman Infotainment 20190525031613 allows root access via SSH over a USB-to-Ethernet dongle with a password that is an internal project name.

## Which versions are affected by CVE-2023-40291?

It affects 1 product.


Products: Samsung Harman Infotainment.

## How do I fix CVE-2023-40291?

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

## Is CVE-2023-40291 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-40293](https://insights.sbomify.com/CVE-2023-40293/): Command injection in n/a (medium 6.8)
- [CVE-2023-40292](https://insights.sbomify.com/CVE-2023-40292/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40291 and fix it if it is affected.

What it is: CVE-2023-40291 is a medium-severity vulnerability in n/a, published on 14 Aug 2023. 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-2023-40291 exists.

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-2023-40291/ (Markdown: https://insights.sbomify.com/CVE-2023-40291/index.md)
```

## Sources

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

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